I am posting my findings here to help shed insight as to the Out of Memory error my users are getting. This may give you clues as to help identify your issue and any possible work arounds.
The file I am using is 17MB in size and has 23 pages. This document was scanned and e-mail to our team, so the large size is related to the scanned documents and scanner settings.
We are Windows 10
Adobe Acrobat Pro 32bit version 2021.007.20091
My original comment with detailed troubleshooting and observations below:
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.
Here is my baseline computer stats are:
CPU: ~4%
Processes: 239 (I have a lot of software installed)
Memory: 5.8GB of 15.8GB (Physical)
Memory: 8.3GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 8-155kbps (no activity)
Disk usage: 0-1% (no activity)
Document First Opened
CPU: 4-11%
Processes: 239 (I have a lot of software installed)
Memory: 6.2 of 15.8GB (Physical)
Memory: 8.7GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 1.1Mbps
Disk usage: 0-1% (no activity)
*At this point Adobe is using 330MB of RAM.*
Document Organized Pages Opened
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 7.1 of 15.8GB (Physical)
Memory: 9.8GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
*At this point Adobe is using 1,250.9MB of RAM., 4x the orignal size)
Document Extract First Page (viewing Extracted tab document)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 7.1 of 15.8GB (Physical)
Memory: 9.7GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
*At this point Adobe is using 1,240.7MB of RAM.*
Document Extract First Page (viewing Original document tab)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 8.2GB of 15.8GB (Physical)
Memory: 10.8GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
*At this point Adobe is using 2,208.7MB of RAM nearly a 1GB increase)
Document Extract First Page (viewing Extracted tab document, again)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 8.1GB of 15.8GB (Physical)
Memory: 10.8GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
Document Extract First Page (Closed Extracted File, back to original document)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 7.7GB of 15.8GB (Physical)
Memory: 10.7GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
Document Extract Second Page (viewing Extracted tab document)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 7.7GB of 15.8GB (Physical)
Memory: 10.8GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
Document Extract Second Page (viewing Original document tab)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 8.6GB of 15.8GB (Physical)
Memory: 11.7GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
*At this point Adobe is using 3,290.9MB of RAM.*
Document Extract Second Page (Closed Extracted File, back to original document)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 8.5GB of 15.8GB (Physical)
Memory: 11.7GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
*At this point Adobe is using 3,274.4MB of RAM.*
Document Extract Third Page (viewing Extracted tab document)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 8.6GB of 15.8GB (Physical)
Memory: 11.8GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-1% (no activity)
*At this point Adobe is using 3,346.1MB of RAM.*
Document Extract Third Page (viewing Original document tab)
CPU: 4-11%
Processes: 238 (I have a lot of software installed)
Memory: 8.8GB of 15.8GB (Physical)
Memory: 12.0GB of 24.8GB (Physical+Virtual/Paging File)
Ethernet: 0 - 1.1Mbps (reduced load, rarely spikes)
Disk usage: 0-2% (no activity)*At this point Adobe is using 3,514.9MB of RAM.*
*System Memeory is at 55%*
*Tiles on Orgainze Pages have failed to load half way through.*
At this point I closed the 3rd extracted file and went to open a 4th and got the out of memory error.
This proves that memory is not being handled properly and we are hitting the 32bit software install memory limits.
Other posts have made reference that the tile views of Adobe are causing issues for them as well.
Unless your computer's physical and virtual memory is being maxed out, your PC should be running just fine and it is the Adobe applicaiton that needs to close to free up memory. As long as you have some sort of physical memory and virtual memory availiable this error should only be an issue with lost productivity/work. If there is a 64bit (I haven't even looked it to to confirm), this issue may be worse for those people, if even present.
What I have viewed is every time I went back to the tiled view, the individual pages had to reload and Adobe is either not dumping the old data, or is not pulling from that chached data, but loading it into memory after each change.
***** Now this has been following what my users have been doing, when extracting pages, they also select "Delete Pages after extracting". It stands to reason, that whatever bloat is happening is being reloaded because the source document is being changed after each extraction. So there could be multiple copies/change settings hiding within the original file. This could and most likely should be expected behavior, the memory bloat by several hundread MB/GB for a 17MB file should not. *****
***** The "Fix" *****
In my users case, we need to stop using the Delete Pages after extracting option, until there is an actual fix. I am 99% sure this is also related to the tile view "out of memory" error repoted on others on the discussion board. There is some kind of bloat with tiles in Adobe. A saving grace is that because we are using 32bit applications we have avoided total lockups from memory use as the 32bit applicaiton can't max out the resources of what my users have.
1
Reply
AdChoices