Memory leak on PC

Report · Nov 20, 2022

After a recent update (I don't remember the original version, but I downloaded After effects from scratch a month or two ago), my After effects keep building up my memory until it hits its maximum allocated memory and after a few seconds it crashes. When editing, this memory build up is slow and can be managed by clearing the cache, saving often or whatnot, but when trying to render it only takes about one minute for After effects to crash completely. I have tried other past versions, cleaning my computer completely and reinstalling both new and old versions (in multiple installations) but it keeps happening.

My computer is very new and I have rendered one video since. After trying to make a second and shorter video, this bug started to appear in every scenario imaginable surrounding this particular video. The only new thing that I implemented in this new video is CC Flo Motion (throughout the video). Rendering is slower because of it, and I understand that this is normal, but crashing relentlessly is not normal at all. I'll post the debug analysis from WinDbg below.

This problem is extremely frustrating as I cannot complete my work with it. I have tried many solutions from limiting / allowing many memory related parameters in AE and nothing seems to work. I'm willing to pay for an expert checkup if such a thing exist because I cannot allow further impediments.

Here are my computer specs:
Device name DESKTOP-DUSD3AD
Processor AMD Ryzen 7 5800X 8-Core Processor 3.80 GHz
Installed RAM 32.0 GB
Device ID BDD77417-C525-49E9-9528-E0C8DF29E656
Product ID 00330-81493-28305-AA725
System type 64-bit operating system, x64-based processor
Edition Windows 10 Pro
Version 21H2
Installed on ‎2022-‎10-‎03
OS build 19044.2251
Experience Windows Feature Experience Pack 120.2212.4180.0

Here is the debug analysis:

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(25f4.11b8): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v*** WARNING: Unable to verify checksum for ntdll.dll
*** WARNING: Unable to verify checksum for KERNELBASE.dll
ntdll!NtDelayExecution+0x14:
00007ffd`80b6d744 c3              ret
0:192> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify checksum for PF.dll
*** WARNING: Unable to verify checksum for dvacore.dll
*** WARNING: Unable to verify checksum for KERNEL32.DLL
*** WARNING: Unable to verify checksum for ole32.dll
*** WARNING: Unable to verify checksum for twinapi.appcore.dll

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 624

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1325

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 233

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3521

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 128

    Key  : Timeline.Process.Start.DeltaSec
    Value: 125

    Key  : WER.Process.Version
    Value: 22.6.0.64


FILE_IN_CAB:  c80105ea-6403-4c3f-99e1-c84d339d7c17.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

CONTEXT:  (.ecxr)rax=ffffffffffffff8b rbx=0000000080000001 rcx=0000000000000000
rdx=0000000107d8ff2c rsi=00000011294cf1e4 rdi=0000000000001f3f
rip=00000000229bccdc rsp=0000000128d0f0e0 rbp=0000000000000001
 r8=0000000080000000  r9=0000000000000000 r10=0000000000000000
r11=00000000a57f5e28 r12=0000000000000000 r13=0000000128d0f630
r14=0000000080000000 r15=0000000000000003
iopl=0         nv up ei pl nz na pe cy
cs=0033  ss=0000  ds=0000  es=0000  fs=0053  gs=002b             efl=00010203
Sphere!MainEntry+0x8d1c:
00000000`229bccdc 0fb602          movzx   eax,byte ptr [rdx] ds:00000001`07d8ff2c=??
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)ExceptionAddress: 00000000229bccdc (Sphere!MainEntry+0x0000000000008d1c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000107d8ff2c
Attempt to read from address 0000000107d8ff2c

PROCESS_NAME:  AfterFX.exe

READ_ADDRESS:  0000000107d8ff2c 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000107d8ff2c

STACK_TEXT:  
00000001`28d0f0e0 00000000`229b7624     : bcc00000`00000000 00000011`294cf1e4 00000000`0b868280 00007ffd`80af5ba1 : Sphere!MainEntry+0x8d1c
00000001`28d0f190 00000000`0b643db8     : 00000011`294cc2c4 00000000`00001771 0000005a`8f0363dc 00000000`00001405 : Sphere!MainEntry+0x3664
00000001`28d0f4d0 00000000`0b645590     : 00000000`e39f4db0 00000000`00000001 00000000`00001770 00000000`0000176f : PF!PF_Interleave1to4<float>+0x1638
00000001`28d0f570 00000000`0b5f5e0b     : 00000000`00000020 00000000`096f3d80 00000000`262ab740 00000000`096f3d88 : PF!PF_IterateOrigin+0x710
00000001`28d0f7a0 00000000`0b5f681f     : 00000000`2746f468 00000000`1a063590 00000000`00000000 00000001`28d0faa8 : PF!PF_AdvancedFrameBlending::Render+0x537b
00000001`28d0f7f0 00000000`092d9e4a     : 00000001`28d0fa00 00007ffd`63ef989f 00007ffd`00000000 00000000`f3fccdf0 : PF!PF_AdvancedFrameBlending::Render+0x5d8f
00000001`28d0f860 00000000`092bab67     : 00000000`c98db500 00000000`00000001 00000000`19772d01 00000000`092d5af6 : dvacore!dvacore::threads::CurrentThreadIsMainThread+0x6a
00000001`28d0f8b0 00000000`092be2c3     : 00000000`c98db500 00000000`c98db500 00000000`19772d80 00000000`19772d88 : dvacore!dvacore::test::Terminate+0x5d37
00000001`28d0f900 00000000`092c3ee6     : 00000000`00000001 00000000`c9ae8f80 00000000`bc5c5b70 00000000`000011b8 : dvacore!dvacore::threads::CreateSubExecutorWithFunctionWrapper+0x3203
00000001`28d0fa90 00000000`092e3c53     : 00000000`00000000 00000000`00000000 00003f21`d3cb8806 00007ffd`80b24364 : dvacore!dvacore::threads::AdaptCurrentEventLoopAsExecutor+0x756
00000001`28d0fb20 00007ffd`80b3fcd3     : 00000000`c9ae8f80 00000000`7ffe0386 00000000`00000006 00000000`00000000 : dvacore!dvacore::threads::GetProcessIDsForName+0xcb3
00000001`28d0fb50 00007ffd`80b231aa     : 00000000`00000000 00000000`c9ae8f80 00000000`092e3c40 00000000`00000000 : ntdll!RtlpTpWorkCallback+0x173
00000001`28d0fc30 00007ffd`803d74b4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x68a
00000001`28d0ff30 00007ffd`80b226a1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14
00000001`28d0ff60 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


SYMBOL_NAME:  Sphere+8d1c

MODULE_NAME: Sphere

IMAGE_NAME:  Sphere.aex

STACK_COMMAND:  ~192s; .ecxr ; kb

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_Sphere.aex!Unknown

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e8da3d00-23f8-b1f3-6d66-49abcec2df0d}

Followup:     MachineOwner
---------

Report · Nov 21, 2022

The problem seemed to be with the file itself. Before I updated manually, perhaps another update was carried out automatically and then my file was somehow corrupted. I am currently rendering a new video under version 22.6 and it has similar effects and although my memory is capped during the render it is no longer crashing.

Sadly the fix was to go back into more stable versions and restart my whole video from scratch. At least I know exactly what to do and the process will be much quicker than before. Message me if you want further details on my debug process (or in this thread if it is not locked yet), but my help could be of no use considering my solution was to basically start over. Perhaps an expert on AE could provide a more satisfying answer under this thread.

Report · Nov 21, 2022

Hi @William2679513905go,

Thank you for reporting this issue and for all the details you've shared. Would it be possible for you to share the problematic file with our team? Have you submitted a crash report after After Effects crashes?

The debug analysis appears to point to a crash in CC Sphere. Are you using that effect in your project?

Thanks for reporting this issue and for any further information you can provide,

- John, After Effects Engineering Team

Report · Nov 22, 2022

Sure, could I share it privately (and how would it be possible)? I also removed the audio files if you don't mind, I don't think they are relevent to the problem anyway.

Since I restarted this project in another new file the problem does not resurface, just to be clear. I am also using the same effects and imported files.

Report · Dec 20, 2022

Hi @William2679513905go,

Yes, feel free to message me directly here on the forums with the leaking/crashing project. Glad to here that a new project seems to avoid the issue as well. You might also try updating to the latest After Effects 23.1 (released last week) which contains some fixes for memory-related issues.

Cheers,

- John, After Effects Engineering Team

Report · Sep 28, 2023

I'm experiencing a similar issue, did you manage to solve the problem?

Adobe Community

Memory leak on PC