Out of Memory

We have the same problem for a week on 3+ computers. The memory goes up to 3GB and the out of memory message comes up. Restarting the PC is no solution. We are working in the printing field and have a lot of PDF-Files to check every day.

OS: Windows 10 Pro 21H1 / 64 bit /

Acrobat Version (32 bit): 2021.007.20091

Enfocus Pitstop Pro: 2020 Update 1

Prinect PDF-Toolbox 2020: 20.00.049

I have a team of people getting the same thing when trying to extract pages from larger documents (about 10-20MB in size, 20-80 pages).

What I have noticed is when we are on Organize pages, memory usage spikes considerably.  As an example, opening a 17MB document loads to about 200-300MB in memory, fine great, normal behavior.  But clicking on Organize pages, skyrockets the usage to 1,000MB (1GB) of RAM in use.  Pretty sure that isn't expected behavior, but whatever it is an 8GB machine at 60% memory load, so no issue yet.  Extracting a single page to a new tab, tends to decrease memory usage by about 100MB.  Odd, but whatever.  Closing the newly opened tab and returning to the original document is when it gets interesting.  Memory usage spikes again between 500-1000MB's and compounds on each extracted file when closed.  Ok, so I close out of the Organize Pages mode thinking memory will return to normal... it doesn't.  I close the document, but leave Adobe up, it doesn't dump the memory either.  When it hits about 3400MB of memory, that is when I get the error.  The only way to flush it is to exit out of Adobe and open it back up.  This problem is compounded because to clear out a 60 page document it requires it to be opened 10-15 times since the users can only work on 3-6 extractions at a time.

I would vote to uninstall/reinstall, but this issue is running present across multiple users, my own included to test with.  Everything is up to date.  Tried messing with Protection and Cache settings, which only reduced the inital file load of 50MB give or take, but did nothing to stop the root issue.  

There was a workaround I found by resaving the file through "reduced" file size, but this isn't a solution, and it requires the end user to be aware of factors they are not trained to look for, let alone remember mid operation.