Community Discussion: Slowdowns and Not Enough Memory to Proceed errors >
> Found at:formatting link
> >
> "Starting recently (perhaps with the R44.28 release?), I've noted that I must exit and restart Quicken frequently (i.e. once or twice per day) or it gets progressively slower and, eventually, starts throwing up 'Not Enough Memory to Proceed' errors."
> Then later >
> "One thing I have noted is that doing a One-Step Update seems to correlate to the slowdown becoming worse, and the memory error tends to occur when reconciling transactions immediately after the update.
> And > "What I've discovered is that, as I click into each account for the first time during a process session, some number of User and GDI resources are consumed (User objects in particular). This happens once per account, presumably as Quicken loads its register window into the process space. Because Quicken keeps registers open in the background even when you switch to another account, those resources are not de-allocated until the process closes (which is expected).
>
> "However, when I do a One Step Update, Quicken then leaks another large set of User and GDI objects, the size of the leak being proportional to the number of accounts I've clicked into (i.e. that are open in memory). For example, if I do a One Step Update immediately after launching the program and without opening any accounts, there is effectively no leak. However, if I toggle thru 10 or so accounts to load the registers into memory and then perform a One Step Update, I can leak hundreds or even thousands of User/GDI objects (see the qw-objects.png for a view of Task Manager after an update).
>
> "Because the Windows process limit for User objects is 10K, I only need to update twice to exhaust the User object limit.
> Quicken then crashes, sometimes after showing the 'Not Enough Memory to Proceed' error.
> I uploaded a crash report from Quicken's crash screen today."
> I have seen the same problem while testing R45.13.
Apparently fixed in R46.12.