Ask a Question
GoPro Support Hub Find a solution. Share a solution. Ask a question. Stay stoked.
Announcements
Is your GoPro gear up to date? Check to see If it is on our Update page.
GoPro Apps for Desktop
%3CLINGO-SUB%20id%3D%22lingo-sub-239122%22%20slang%3D%22en-US%22%3EFusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239122%22%20slang%3D%22en-US%22%3E%3CP%3EFusion%20Studio%201.3%3C%2FP%3E%3CP%3EWindows%2010%20Enterprise%3C%2FP%3E%3CP%3E16GB%20memory%2C%2016GB%20pagefile%3C%2FP%3E%3CP%3ERender%20settings%20set%20to%20%22Editing%22%2C%20%225.2K%22%2C%20%22360%20Audio%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2FGoPro-Apps-for-Desktop%2FFusion-Studio-1-0-Memory-error-Crashes-Constantly%2Ftd-p%2F85157%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcommunity.gopro.com%2Ft5%2FGoPro-Apps-for-Desktop%2FFusion-Studio-1-0-Memory-error-Crashes-Constantly%2Ftd-p%2F85157%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.reddit.com%2Fr%2Fgopro%2Fcomments%2F7efi32%2Ffusion_studio_crashes%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.reddit.com%2Fr%2Fgopro%2Fcomments%2F7efi32%2Ffusion_studio_crashes%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeems%20this%20has%20been%20an%20issue%20since%20version%201.0%2C%20and%20still%20exists%20today%20on%20version%201.3.%20When%20the%20leak%20is%20present%2C%20Fusion%20Studio%20can't%20get%20through%20rendering%20a%20single%20video%20without%20crashing%20after%20using%20up%20all%20of%20my%20system's%20memory%20(16GB%20ram%20%2B%2016GB%20pagefile).%20It%20gets%20to%20about%2040%25%20on%20the%20render%20before%20~39GB%20of%20memory%20is%20committed%20and%20the%20app%20crashes.%20This%20is%20on%20a%201%20minute%2030%20second%20clip.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20only%20started%20happening%20after%20I%20added%20about%2050%20videos%20to%20the%20render%20queue%20and%20tried%20to%20render%20them%20over%20night%2C%20and%20it%20couldn't%20get%20through%20the%20first%20one%20(short%201-2%20minute%20clip)%20without%20crashing.%20Previously%20I%20had%20only%20rendered%20one%20or%20two%20videos%20on%20the%20queue%20at%20a%20time%2C%20which%20it%20seemed%20to%20handle%20OK%20(I%20didn't%20monitor%20ram%20usage%20at%20the%20time%2C%20no%20idea%20how%20much%20it%20took%20up).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20reducing%20the%20render%20queue%20from%2050%20videos%20to%208%2C%20and%20it%20still%20couldn't%20get%20through%20the%20first%20without%20using%20up%20all%20my%20memory%20and%20crashing.%20I%20then%20tried%20reducing%20it%20to%202%2C%20no%20difference.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20decided%20at%20this%20point%20to%20forget%20restoring%20my%20previous%20session%20and%20start%20from%20a%20new%20one.%20Added%20one%20video%20to%20the%20render%20queue%20(1%20min%2030%20second%20clip)%20and%20hit%20render.%20This%20time%20when%20it%20got%20to%2040%25%2C%2014.1GB%20of%20memory%20was%20in%20use%2C%2027.3GB%20committed.%20At%2050%25%2C%2014.8GB%20in%20use%2C%2027.9GB%20committed.%20At%2060%25%2C%2015.1GB%20in%20use%2C%2028.3GB%20committed.%20At%2070%25%2C%2015.2GB%20in%20use%2C%2028.3GB%20committed.%20At%2080%25%2C%2015.3GB%20in%20use%2C%2028.5GB%20committed.%20At%2090%25%2C%2015.2GB%20in%20use%2C%2029.7GB%20committed.%20At%2099%25%2C%2015.3%20GB%20in%20use%2C%2030.2GB%20committed.%20No%20crash.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20that%20I%20closed%20Fusion%20Studio%20to%20start%20a%20new%20session.%20Added%2015%20videos%20to%20the%20render%20queue%20(most%20of%20these%20are%20under%20a%20minute%20long%2C%20with%202%20of%20them%20being%20~10%20minutes%20long%2C%20and%202%20being%20~7%20minutes%20long).%20It%20got%20through%20the%20first%20clip%20(30%20seconds)%20without%20issue%2C%20but%20crashed%20on%20the%202nd%20clip%20(1%20minute)%20about%20half%20way%20through%20(15.9GB%20100%25%20of%20memory%20in%20use%2C%2039.2GB%20committed).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20the%20issue%20might%20lie%20with%20sessions%20with%20larger%20render%20queues%2C%20and%20once%20this%20issue%20is%20present%2C%20even%20clearing%20the%20queue%20down%20to%201%20video%20doesn't%20solve%20it%2C%20you%20need%20to%20start%20a%20new%20session%20and%20render%20one%20or%20two%20videos%20at%20a%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20there's%20any%20crash%20dumps%20I%20can%20upload%20I'd%20be%20happy%20to%20submit%20them.%20The%20usual%20upload%20crash%20log%20dialogue%20didn't%20pop%20up%20after%20any%20of%20the%20crashes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-239122%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EGoPro%20Fusion%20Studio%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239649%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239649%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20seems%20the%20size%20of%20the%20render%20queue%20may%20not%20matter.%20Just%20tried%20to%20render%20one%20video%20(1%20minute%20clip)%20and%20it%20didn't%20even%20get%20half%20way%20before%20taking%20up%20all%20my%20system's%20memory%20and%20crashing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-240117%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240117%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20having%20this%20issue%20too%20with%20Windows%2010%20Professional.%3C%2FP%3E%3CP%3E32GB%20RAM%2C%201TB%20pagefile%20(set%20it%20to%20that%20for%20testing)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E15%20minute%20video%2C%20set%20it%20to%20render%205.2K%20at%20all%20highest%20settings.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFusion%20Studio%20used%20all%20of%20my%20RAM%20and%20around%20300GB%20of%20the%20pagefile%20before%20the%20app%20crashed.%20I%20sent%20in%20crash%20reports%20multiple%20times%2C%20so%20hopefully%20this%20helps%20the%20devs%20track%20down%20the%20cause.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-240260%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240260%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20the%20feedback%20and%20the%20detailed%20description%20of%20the%20matter%2C%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F75261%22%20target%3D%22_blank%22%3E%40rockysand61858%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F75464%22%20target%3D%22_blank%22%3E%40coolpike35853%3C%2FA%3E%20.%20We%20will%20submit%20this%20to%20the%20team%20for%20a%20closer%20look.%20We'll%20keep%20you%20posted.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253175%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253175%22%20slang%3D%22en-US%22%3E%3CP%3Eany%20update%20on%20this%3F%26nbsp%3B%20Fusion%20Studio%20is%20essentially%20useless%20right%20now%2C%20I%20cannot%20stitch%20any%20videos%20without%20crashing%20due%20to%20out%20of%20memory%20exceptions.%26nbsp%3B%20is%20there%20another%20version%20we%20can%20test%3F%26nbsp%3B%20if%20not%2C%20when%20will%20it%20be%20released%3F%26nbsp%3B%20is%20anyone%20even%20listening%3F%26nbsp%3B%20I%20have%20lost%20all%20faith%20in%20the%20GoPro%20brand%20after%20this%20Fusion%20fiasco.%26nbsp%3B%20probably%20should%20have%20not%20released%20the%20camera%20with%20such%20crap%20software%20until%20it%20was%20fixed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253593%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253593%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F43718%22%20target%3D%22_blank%22%3E%40dw450%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20to%20hear%20about%20the%20trouble.%20We%20are%20still%20waiting%20for%20an%20update%20from%20the%20team.%20Alternatively%2C%20you%20can%20contact%20our%20Support%20team%20for%20a%20more%20personalized%20support.%20This%20way%2C%20a%20case%20can%20be%20established%20and%20the%20Fusion%20team%20can%20walk%20you%20through%20additional%20steps.%20You%20can%20reach%20the%20team%20through%20phone%20or%20chat%20here%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgopro.com%2Fhelp%2FContactUs%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgopro.com%2Fhelp%2FContactUs%3C%2FA%3E%20.%26nbsp%3BLet%20us%20know%20how%20it%20goes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%26nbsp%3B%3CBR%20%2F%3E%20Marius%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276388%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276388%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20the%20same%20issue%20and%20getting%20really%20fed%20up%20since%20I%20just%20had%20to%20setup%20a%202nd%20PC%20to%20even%20get%20it%20to%20run%20(first%20was%20a%20Dell%20XPS%2015%209575%20with%208th%20gen%20Intel%20CPU%2C%20Intel%2FAMD%20on-board%2C%20then%20GTX%201080%20in%20eGPU%20over%20tb3).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIronic%20that%20GoPro%20gave%20me%20so%20much%20attitude%20(when%20they%20were%20they%20were%20no-where%20near%20as%20capable%20as%20we%20were)%20in%20the%20early%20days%2C%20when%20I%20was%20breaking%20new%20ground%20(live-stitching%20and%20streaming%20G'n'R%20from%20Coachella%2C%20for%20YouTube)%20doing%20live%20stitching%2C%20and%20now%20I'm%20just%20another%20annoyed%20consumer%20of%20there's.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETime%20to%20go%20see%20what%20stitching%20package%20will%20pick%20up%20the%20slack%20today%20because%20after%206%20months%20of%20wasting%20time%20with%20Fusion%2C%20I've%20had%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276393%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276393%22%20slang%3D%22en-US%22%3E%3CP%3EMore%20searching%20led%20me%20to%20the%20following%20and%20after%20switching%20to%20stereo%20audio%2C%20it%20looks%20like%20my%20stitching%20jobs%20are%20running%20now%2C%20without%20the%20ram%20leak.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps%20someone%20else.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2FCameras%2FGoPro-Fusion-Studio-1-3-ALWAYS-crashing-when-using-360-Audio%2Ftd-p%2F245878%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcommunity.gopro.com%2Ft5%2FCameras%2FGoPro-Fusion-Studio-1-3-ALWAYS-crashing-when-using-360-Audio%2Ftd-p%2F245878%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-277792%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-277792%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20the%20same%20problem%2C%20can't%20even%20render%20a%2030%20seconds%20video%20without%20having%20to%20constantly%20pause%20the%20process%20to%20keep%20the%20program%20from%20crashing%2C%20I%20have%2032GB%20of%20RAM%2C%20an%20i7%204790k%2C%20a%20GTX1080ti.%20Thinking%20on%20returning%20the%20camera%20since%20GoPro%20seems%20to%20have%20completly%20abandon%20this%20product%2C%20the%20Fusion%20is%20my%20first%20GoPro%20camera%20and%20for%20all%20this%20it%20seems%20it%20will%20be%20my%20last.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281866%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281866%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%0A%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82611%22%20target%3D%22_blank%22%3E%40ernf1107%3C%2FA%3E%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%0A%3CP%3EWhat%20were%20the%20rendering%20options%20you%20have%20selected%3F%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%0A%3CP%3EPlease%20see%20information%20listed%20on%20this%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2FGoPro-Apps-for-Desktop%2Fgopro-fusion-studio-1-3-uses-16gb-memory-then-crashes%2Ftd-p%2F262068%22%20target%3D%22_blank%22%3Ethread%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%0A%3CP%3EThanks!%3C%2FP%3E%0A%0A%3CP%3EEj%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281974%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281974%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F84110%22%20target%3D%22_blank%22%3E%40rainabba%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EMore%20searching%20led%20me%20to%20the%20following%20and%20after%20switching%20to%20stereo%20audio%2C%20it%20looks%20like%20my%20stitching%20jobs%20are%20running%20now%2C%20without%20the%20ram%20leak.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps%20someone%20else.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.gopro.com%2Ft5%2FCameras%2FGoPro-Fusion-Studio-1-3-ALWAYS-crashing-when-using-360-Audio%2Ftd-p%2F245878%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcommunity.gopro.com%2Ft5%2FCameras%2FGoPro-Fusion-Studio-1-3-ALWAYS-crashing-when-using-360-Audio%2Ftd-p%2F245878%3C%2FA%3E%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EThanks%20for%20the%20tip.%20Looks%20like%20the%20issue%20is%20with%20the%20Cineform%20codec%20and%20360%20audio.%20You%20can%20render%20with%20360%20audio%20if%20you%20chose%20ProRes%20but%20the%20filesize%20will%20be%20about%20twice%20as%20big.%20At%20least%20I%20can%20actually%20render%20now%20on%20ProRes%20until%20GoPro%20gets%20their%20**bleep**%20together.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282009%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282009%22%20slang%3D%22en-US%22%3E%3CP%3EI%20stopped%20the%20problem%20when%20I%20selected%20stereo%20audio%20instead%20of%20surround%20audio.%20Selecting%20ProRes%20422%20with%20surround%20may%20help.%20Hope%20you%20have%20the%20original%20video%20data%20to%20re-render.%20This%20is%20a%20work%20around%20not%20cure!%20and%20the%20software%20needs%20more%20work%20on%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287284%22%20slang%3D%22en-US%22%3ERe%3A%20Fusion%20Studio%201.3%20memory%20leak%20(on%20larger%20render%20queues)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287284%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20confirm%20that%20stereo%20audio%20fixes%20the%20problem%20for%20regular%205.2k%20Cineform%20videos%2C%20however%20the%20problem%20persists%20if%20you%20are%20trying%20to%20render%20timelapses%20at%205.2k%20cineform%3C%2FP%3E%3C%2FLINGO-BODY%3E
Reply
Highlighted
Hiker
Posts: 11

Re: Fusion Studio 1.3 memory leak (on larger render queues)

I'm having the same problem, can't even render a 30 seconds video without having to constantly pause the process to keep the program from crashing, I have 32GB of RAM, an i7 4790k, a GTX1080ti. Thinking on returning the camera since GoPro seems to have completly abandon this product, the Fusion is my first GoPro camera and for all this it seems it will be my last.

GoPro
Posts: 8,889

Re: Fusion Studio 1.3 memory leak (on larger render queues)

 

Hi @ernf1107

 

What were the rendering options you have selected?

 

Please see information listed on this thread

 

Thanks!

Ej

Tourist
Posts: 3

Re: Fusion Studio 1.3 memory leak (on larger render queues)


@rainabba wrote:

More searching led me to the following and after switching to stereo audio, it looks like my stitching jobs are running now, without the ram leak.

 

Hope this helps someone else.

 

https://community.gopro.com/t5/Cameras/GoPro-Fusion-Studio-1-3-ALWAYS-crashing-when-using-360-Audio/...


Thanks for the tip. Looks like the issue is with the Cineform codec and 360 audio. You can render with 360 audio if you chose ProRes but the filesize will be about twice as big. At least I can actually render now on ProRes until GoPro gets their **bleep** together.

Hiker
Posts: 14

Re: Fusion Studio 1.3 memory leak (on larger render queues)

I stopped the problem when I selected stereo audio instead of surround audio. Selecting ProRes 422 with surround may help. Hope you have the original video data to re-render. This is a work around not cure! and the software needs more work on it.

Hiker
Posts: 11

Re: Fusion Studio 1.3 memory leak (on larger render queues)

I can confirm that stereo audio fixes the problem for regular 5.2k Cineform videos, however the problem persists if you are trying to render timelapses at 5.2k cineform