Adobe Reader 8 memory leak

There seems to be a private byte memory leak with Adobe Reader 8.0.0 and 8.1.2 (tested both) when you try to print a PDF document. If you monitor the private bytes usage of the AcroRD32.exe with perfmon and then try to print you will see the memory usage jump and it does not come back down after the print job. In fact, it keeps on rising as you keep on sending a new print job. The only way to release the memory is to close the document and reopen it.

>I have more than 700 MB virtual memory.
That's probably not enough for normal operations. A couple of
gigabytes is safer.
There may be a problem, though. This doesn't sound like normal
behaviour. Acrobat may be cacheing text - does the size stop
increasing if you search for something, and find it, on the LAST page?
Aandi Inston

Similar Messages

Adobe Story memory leak

I am running Adobe Story online in Windows 7 Ultimate, 64-bit, using the application on my desktop. In the Task Manager, the Memory for Adobe Story constantly increases. At the moment it's 160,000 KB and climbing. If I leave it open for any length of time, all functions in it slow way down, apparently the result of what appears to be a memory leak.
Jeff Sengstack

Adobe, can you hear me?
Not guaranteed when posting here. Try below instead.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Having said that, this is not a problem I see on any of the four Windows machines I work on. And it's not a problem commonly reported here. So my inclination is to suggest that something may be funky with your install.

Adobe Reader X leaks GDI handles in quick search box

Just installed Adobe Reader X a couple of days ago (Windows 7, x64). I used it for numerous online documents (in Firefox), while searching for some specific terms in each document. After a while the reader presented a strange picture, not properly painting itself anymore. Then, the reader became unresponsive, and Firefox too, and I had to kill the task.
This happened a few times on different pdf documents.
In my programming career things like these have happened more often so, when the behavior happened again, I went checking the process using Windows Task Manager, adding a few extra columns (Handles, User Objects, GDI Objects) and found that the number of GDI objects was nearly 10000, the absolute limit that Windows imposes on any single process.
I went on checking the reader, now standalone and without Firefox, to see if the problem would persist. Opened a few pdfs and scrolled back and forth. No problems -
tried the same in Firefox to see if the plugin was OK - still no problem.
Then started using the quick search box (Ctrl-F) and repeatedly looked for something trivial (e.g. just a single letter A) - Bingo! Now the GDI handle count starts rising seriously, and does not come back to the original level.
This is definitely a leak, and it needs to be fixed.

We don't process bug reports via these forums - please post any details of unexpected behaviors to the official reporting form.

Adobe AIR memory leak loading SWFs

I was plagued by a memory leak that would crash my application after a few hours. The application had worked fine in the past but now was having issues and I thought it might have to do with using newer SDK's.
In the end I discovered that if I loaded external swf that had been compiled in debug mode, they would not clear completely on unload and cause a memory leak.
Compiling in release mode fixed the issue. Spent 3 days trying to figure it out.

Any chance you can check that out with the latest AIR?
Either way, it sounds like a bug, please report it at http://bugbase.adobe.com/ and then report the bug number here.
If you're able to provide a reproducable case that would really increase the chance that we can do something about it.
Thanks,
roymeo

Strange adobe reader memory usage while selecting text or just holding the click.

Hi,
I have observed this increase in cpu usage since the ubuntu 8.10, when I started using acroread.
I thought it gonna improve in the near future, but it still exists, and I am not able to find someone who has seen or reported this.
Currently I am using Ubuntu 11.10 64 bit and adobe reader's version is 9.4.7.
Try reproducing it, just by opening any text pdf document and selecting some text, dont release the left click, keep it holding and it eats full cpu, until you leave it.
System Load Indicator shows a sudden and full increase in usage.
Any one having any idea about it. You cannot report it as Ubuntu bug because adobe is external software.
This is not observed in the web pdf document downloaded and opened in web browser using same adobe's reader.
Cheers
Sukhi

I've just started experiencing the exact same problem. I upgraded to Reader X a good month or so ago, and I've had it open with documents loaded for long stretches most days since installing it, but I didn't notice the problem until Sunday 9th Jan. Closing Reader and reopening it brings back the toolbar, but then it disappears again after a while.
I too am running Windows XP SP 3, with 2 GB RAM and an AMD Athlon 64 X2 Dual Core 6000+ CPU.
Ose

Adobe Aire memory leak?

Hello everyone,
I am a windows xp home user with the lates flash player installed.
I been noticing some were memory usage when i use the adobe air flash player. Im not sure if anyone els notice this problem,
but when ever i launch a software called streamdesk. my memory suddenly jumps to 1.10 gb of memory. but,when i restart my computer my memory is back to normal. is anyone els seeing this problem? if so,we to report it to adobe air so they can fix it...

Adobe, can you hear me?
Not guaranteed when posting here. Try below instead.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Having said that, this is not a problem I see on any of the four Windows machines I work on. And it's not a problem commonly reported here. So my inclination is to suggest that something may be funky with your install.

Memory leak on latest Adobe Reader 8.1.2 Win XP SP2

Dear Adobe Developers,
I have encountered a strange problem. I open a PDF file of size about 16.5 MB, I search trough it and then the memory allocated starts steadily growing until it fills out the entire RAM and the virtual memory as well. Strange thing is this only happens after I perform a search through the file; if I don't do it, all stays within normal. I was wondering if it is not a memory leak of some kind? I use Adobe Reader 8.1.2 on Win XP with Service Pack 2 on Celeron 1.7 GHZ, 256 DDR RAM, 320 GB HDD ect .. Normally the RAM occupied by the OS itself is only about 100 MB so there are ~150MB left free. But they seem not to be enough even when we add to them the virtual memory.
Greetings,
Georgi Popov, BG

>I have more than 700 MB virtual memory.
That's probably not enough for normal operations. A couple of
gigabytes is safer.
There may be a problem, though. This doesn't sound like normal
behaviour. Acrobat may be cacheing text - does the size stop
increasing if you search for something, and find it, on the LAST page?
Aandi Inston

Memory Leak in Adobe Reader 9?

Hello,
I have a C# application with a WebBrowser component in a Form and it opens a certain number of new browser pages with a link to a PDF file.
When I close the main program (Not the individual forms with the browser links for PDFs), I get an Application Error : The instruction "" referenced memory at "". The memory could not be read.
I was using Adobe Reader 9.1.2 but then I uninstalled it and installed Reader 8.1 and I am not getting this error anymore when closing the program. Is there a known issue with memory management in Reader 9? It seems like as I close each form, the Reader still stays in memory and does not release its resources.
Thanks,
Igor

Reader generally stays in memory to be able to work faster the next time it is needed. That was true in version 8 as well. There is something else going on. Please continue this conversataion in the SDK forum.

Adobe Reader 9 Memory Leak?

Hello,
I have a C# application with a WebBrowser component in a Form and it opens a certain number of new browser pages with a link to a PDF file with these arguments appeneded: "#toolbar=0&navpanes=0"
When I close the main program (Not the individual forms with the browser links for PDFs), I get an Application Error : The instruction "" referenced memory at "". The memory could not be read.
I was using Adobe Reader 9.1.2 but then I uninstalled it and installed Reader 8.1 and I am not getting this error anymore when closing the program. Is there a known issue with memory management in Reader 9? It seems like as I close each form, the Reader still stays in memory and does not release its resources. I have tested this on 3 computers and I am getting the same results. I am running XP SP3.
Thanks,
Igor

Smile,
I tried that solution in both C# and managed C++, and it occasionally causes an AccessViolationException in the Dispose method.
I can only assume that this exception is thrown because I delete acrobat and free the unused libraries, and then dispose goes to call the library or libraries to delete the ActiveX object, and the libraries are not there.
I noticed something that seems relevant: It is easy to cause this AccessViolationException by quickly and repeatedly calling the LoadFile method on the acrobat control. Does this mean that all will be well if I avoid calling LoadFile at too small an interval? Is there some kind of event or callback I can use to tell me that it is now safe to call LoadFile again? I will look into this, but would definitely appreciate any input.
----------------------------details about repeating LoadFile calls----------------------------
When LoadFile is first called, a few first chance exceptions of this look come up:
First-chance exception at 0x7c81eb33 (kernel32.dll) in program.exe: Microsoft C++ exception: _ASExceptionInfo at memory location 0x03something.
When LoadFile is called quickly and repeatedly, a bunch of these first chance exceptions are generated. They look exactly the same in C# as in MC++. It is when a lot of these are generated, that subsequently closing the program is most likely to give an AccessViolationException.
----------------------------AccessViolationException details----------------------------
In C#, the output regarding the exception is:
First-chance exception at 0x79e9501d (mscorwks.dll) in BasicIacOCXCS.exe: 0xC0000005: Access violation reading location 0x035fa1c0.
The call stack on crash is:
PDFminimalCaseCSharp.exe!PDFminimalCaseCSharp.Form1.Dispose(bool disposing = true) Line 20 + 0xc bytes
System.dll!System.ComponentModel.Component.Dispose() + 0x12 bytes
etc...
In C++, the solution posted at stackoverflow looks like this:
[System::Runtime::InteropServices::DllImport("ole32.dll")]
extern void CoFreeUnusedLibraries();
System::Void Form1_FormClosing(System::Object^ sender, System::Windows::Forms::FormClosingEventArgs^ e)
    if(axAcroPDF1 != nullptr)
        delete axAcroPDF1;
        Application::DoEvents();
        CoFreeUnusedLibraries();
This code causes the same occasional "AccessViolationException in System.Windows.Forms.dll".
The managed C++ call stack:
1003a1c0()
user32.dll!77d48709()
user32.dll!77d487eb()
[Managed to Native Transition]
System.Windows.Forms.dll!System.Windows.Forms.UnsafeNativeMethods.DestroyWindow(System.Run time.InteropServices.HandleRef hWnd) + 0x10 bytes
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DestroyHandle() + 0x7a bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.DestroyHandle() + 0x150 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.Dispose(bool disposing = true) + 0x1da bytes
System.Windows.Forms.dll!System.Windows.Forms.ContainerControl.Dispose(bool disposing) + 0x1f bytes
System.Windows.Forms.dll!System.Windows.Forms.Form.Dispose(bool disposing) + 0x273 bytes
PDFminimalCase.exe!PDFminimalCase.Form1.Dispose(bool = true) + 0x55 bytes
System.dll!System.ComponentModel.Component.Dispose() + 0x12 bytes
etc...

Adobe Reader X and Windows 7 Enterprise Memory Leak

Hi I am using Adobe Reader X with Windows 7 enterprise when reading a 8000 page document when I do a search I notice that the memory on my machine starts to creep up typically 1Mb per search this will continue to rise to over 300Mb as the document is used until it reaches a point that it freezes the machine, The only way to recover is Ctrl-Alt-Delete and cancel the task. Has this been observed by other users?

Good day,
Could you provide some additional details about both the file and your system's configuration?
What version of Adobe Reader X do you have installed? (Help > About Adobe Reader)
If you haven't updated to 10.0.3, please do so and see if the issue persists.
How was the PDF file you're searching created? (File > Document Properties > What does the PDF Producer line say?)
Are you experiencing this with multiple files?
Have you installed SP1 for Windows 7?
Regards,
David
Acrobat Community Manager
Adobe Systems

Memory Leak Issue for Adobe Access iOS API

Hi,
We are trying to develop an iOS app (with ARC enabled) using Adobe Acces API 4.0 and we have identified that the function [drmManager createDRMSession] has memory leak.
DRMSESSION = [drmManager createDRMSession:METADATA playlist:PLAYLIST error:nil complete:^() {}];
We are using:
DRMSESSION -> weak
METADATA ->strong (as need to share within object)
PLAYLIST ->strong (as need to share within object)
After calling this function, the object is unable to dealloc and most of the leaking object related to networking (such as CFNetwork...)
Is this a known issue for the Adobe Access iOS API or we are missing some key steps.
Any suggestions is appreciated. Thanks in advance.

ans0600, sorry about that, I read Hiroshi's forward too quickly. I've done a little digging and have come up with two work-arounds:
Create a file with ARC disabled to translate the returned object to be an autorelease
declare the returned DRMSession as __unsafe_unretained and use CFRelease, as noted on stackexchange
In the future we may change this method to return an autoreleased object to avoid this issue. Let us know if you have any further questions!

Memory Leak in Adobe Premiere CC on Windows

I installed Premiere CC on Windows 7 ( Intel Core i7-3770K [email protected] GHz, 16GB RAM). Software has a serious memory leak. After less than hour working on a very simple project (no rendering, no effects) memory usage reached 15 GB, at which point Premiere stopped responding. After closing and reopening software memory usage again started to increase. I was testing it by just scrubbing over timeline, no editing, memory usage still slowly crept-up. I called Adobe technical support, they tried to tell me, that this is normal. Right! It is normal to be forced to close and reopen application every hour? I do not think so. I have Premiere CC also installed on my MAC Book Pro, checked memory usage on much bigger project, it was steady, not creeping up, using beween 1 and 2 GB. I checked forums for this problem, there are several posts, but have not found any response from Adobe regarding this.
Update:
Tonight I continued working on same small project, within 2 hours I had to shut down Premiere 3 times. I also limited in setting memory Premier can use, that did not make any difference, usage by Premiere went to maximum - total 16 GB with about 2 GB taken by system and other stuff running. I am monitoring memory usage on resource monitor. Used Physical memory went 100 %, Commit Charge about 60%. This so far happened three times in a row.
Adobe, can you hear me?
Milan
Message was edited by: milan-to
Message was edited by: milan-to

Adobe, can you hear me?
Not guaranteed when posting here. Try below instead.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Having said that, this is not a problem I see on any of the four Windows machines I work on. And it's not a problem commonly reported here. So my inclination is to suggest that something may be funky with your install.

Memory lead in Adobe Reader 9.3

Appears like there is a memory leak in Adobe reader 9.3.0 on Windows Vista. When I open a large document (>36MB) Adobe starts hogging memory - over 1.4GB - and choking the PC) and then it hangs the computer. As soon as adobe is killed (the Program i.e. AcreRd32.exe not the Application i.e. the pdf document), the memory gets freed up and choking is gone. Anyone else noticed this - any fixes from Adobe for this - becoming a pain to live with. The earlier version was far better - didn't cause these issues. This issue has started after I installed the latest update as prompted by Adobe.

Should have been memory leak - not "lead"!

Memory Leak Problem at Adobe LiveCycle Server 9.0

Hi All,
We want to upgrade our system to 9.0. During the performance test we have found memory Leak problem at ALS 9.0. I explain the detailed problematic issue below. Is there any body who has any suggest?
We have Adobe Livecycle ES2 9.0 SP2 installed on WAS 6.1. But also WAS on Windows Server 2008 R2. We call java web services from .Net Web service for generating PDFs.
On Java side “com/adobe/internal/pdftoolkit/services/javascript/GibsonMemoryTracking” class is causing Memory Leak problem at server.
Our .Net Codes. I copied below. First we generate PDF then we convert this pdf to static pdf.
First We call the GeneratePDF function.
public static bool GeneratePdf(Document document, byte[] pdfTemplate)
        try
            //Create a FormDataIntegrationService object and set authentication values
            FormDataIntegrationService formDataIntegrationClient = new FormDataIntegrationService();
            formDataIntegrationClient.Credentials = new System.Net.NetworkCredential(Settings.ALCUserName, Settings.ALCPassword);
            //Import XDP XML data into an XFA PDF document
            ALCFormDataIntegrationService.BLOB inXMLData = new ALCFormDataIntegrationService.BLOB();
            //Populate the BLOB object
            inXMLData.binaryData = System.Text.Encoding.UTF8.GetBytes(document.XmlData);
            //Create a BLOB that represents the input PDF form
            ALCFormDataIntegrationService.BLOB inPDFForm = new ALCFormDataIntegrationService.BLOB();
            inPDFForm.binaryData = pdfTemplate;
            //Import data into the PDF form
            ALCFormDataIntegrationService.BLOB results = formDataIntegrationClient.importData(inPDFForm, inXMLData);
            document.PdfData = results.binaryData;
            Utility.Log("GeneratePdf", "Pdf generated successfully.", LogLevel.Info);
            return true;
        catch (Exception ex)
            document.ReturnCode = "22";
            document.ReturnMsg = "Exception on generating the pdf";
            Utility.Log("GeneratePdf", "Exception: " + ex.Message, LogLevel.Error);
            return false;
Then We call the ConvertPDF function.
public static bool ConvertPdf(Document document)
        try
            //Create a OutputServiceService object
            OutputServiceService outputClient = new OutputServiceService();
            outputClient.Credentials = new System.Net.NetworkCredential(Settings.ALCUserName, Settings.ALCPassword);
            //Create a BLOB object
            ALCOutputService.BLOB inData = new ALCOutputService.BLOB();
            //Populate the BLOB object
            inData.binaryData = document.PdfData;
            //Set rendering run-time options
            RenderOptionsSpec renderOptions = new RenderOptionsSpec();
            renderOptions.cacheEnabled = true;
            //Create a non-interactive PDF document
            ALCOutputService.BLOB results = outputClient.transformPDF(inData, TransformationFormat.PDF, PDFARevisionNumber.Revision_1, false, null, PDFAConformance.B, false);
            document.PdfData = results.binaryData;
            Utility.Log("ConvertPdf", "Pdf converted successfully.", LogLevel.Info);
            return true;
        catch (Exception ex)
            document.ReturnCode = "22";
            document.ReturnMsg = "Exception on converting dynamic pdf to static pdf";
            Utility.Log("ConvertPdf", "Exception: " + ex.Message, LogLevel.Error);
            return false;
Our System Configuration:
Expiry date: Never Version: 9.0.0.0,
GM Patch Version: SP2
Service Pack Version: unknown
ADOBE® LIVECYCLE® PDF Generator ES2
9.0.0.0
SP2
ADOBE® LIVECYCLE® Reader Extensions ES2
9.0.0.0
SP2
ADOBE® LIVECYCLE® Output ES2
9.0.0.0
SP2
We changed some configuration which is suggested by Adobe. But this change does not solve our problem.
Changed Configurations via ADMINUI
Memory Leak Problem which is viewed via wily tool:

Hi Mahir,
Can you attach the results of this performance test where we can see how GibsonMemoryTracking class is causing the memory leak issue.
Also do you see any stackTrace in the LiveCycle server logs related to memory / heap when you run this performance test ?
Thanks,
Simer

Adobe reader x eats up my memory

I run my adobe reader x (10.1.1) on windows 7. In most cases, when i open the first pdf file, everything works fine. Problem occurs when i try to open the second one. The reader stop working and the memory usage goes up to like 1.6 Gb and keeps increasing. I have to end the prcess before it eats up all my memory. But for some other files, like the pdf file from http://unicode.org/charts/PDF/U0370.pdf, i cannot open at all. Is it a universal problem or just a special case happen to me?
Thank you for the reply.

it happens to both. I can see multiple instances of Adobe Reader, only one of them is acquiring large amount of memory
As for the pdf i linked, when i tried to opening it, everything stucked. Two processes of adobe reader were shown in task manager, and one of them used up almost all memeory. So i had to terminated it. For other pdf files which caused problems (when they are opend as a second pdf file), i can always reopen it as a first pdf file without problem. This one is different; i can never open it, no matter open it directly or download it and open it locally. i don't know why.
One thing stranged is that this issue never happened before until two days ago, i used to open 10+ pdf file for paper reviewing.
Thanks for your reply.

Adobe Reader 8 memory leak

Similar Messages

Maybe you are looking for