Does AE 23.6.0 have a known memory leak?

[defaulti1o0r0fybisq]

The AE interface will slow down after a few minutes of working on a media-heavy project (ARRI RAW). Menu dropdowns take a few seconds to unfurl. Clicking a menu item takes a few seconds more. Restarting AE fixes the issue until it happens again. This would be a fairly typical workflow for me and mirrors projects in the past. This feels new. My hardware is testing OK. These freezes are not mirrored system-wide and only happen in AE.

Windows 11, 13900k, 128GB RAM, RTX 4080. The project is set to software only.

[jenkmeister]

Do you have the Character Panel open when this is happening? We've had some reports that menus get slow to respond with the Character Panel open. 

[defaulti1o0r0fybisq]

I think I pinned it down. I kept thinking it was one effect or another causing the issue, but it's not any particular effect. It's the Effect Controls panel in general. If I keep it open for any length of time, even with something simple (like levels) populating the panel, the interface freeze will occur. Just closing that Effects Control panel and reopening it resets the behavior until it happens again. Smells like a VRAM memory leak to me.

[jenkmeister]

Any particular effects in the effects panel that cause this more than others? 

[defaulti1o0r0fybisq]

There isn't a particular effect triggering the issue, but I am working on a different computer today without issues. There may be an effect installed and unused that is triggering the problem.

Today I am on a 5975WX, Windows 10, with 256GB RAM and RTX 4090s. Trapcode and Maxon VFX suite are not updated to the latest. I think the only other difference would be the problem computer has Lockdown 3.0 installed, and this one does not. Still investigating.

[defaulti1o0r0fybisq]

Oh. Today's workstation has dual 60hz monitors, and yesterday's has a single 120hz monitor. That couldn't be it, could it?

[defaulti1o0r0fybisq]

Ok. I've tried everything, including turning off all plugins and this still happens. I think it might be a nuke the install and start over for the next step.

[defaulti1o0r0fybisq · Accepted solution]

OK. All said and done, this issue was a corrupt workspace setting. Nuking all the custom workspaces seemed to fix the issue.