Reader 8.1.2 memory leak??

I finally caught the thing in time, before reader consumed every bit of memory, RAM and swap, locking up my workstation.
top showed 2 instances of acroread, each with 47%+ of memory, and the OS swapping like hell.
Fedora 8, current updates - 3.0 G P4, 2 G ram
I've had this happen a couple of times, resulting in a reset to get t back. I just happened to catch before it rendered my WS useless.
Anyone else?

I encountered this problem also and reported it to Ubuntu as bug #236219 and Medibuntu bug #236433 but both were rejected because it's closed-source. This is what I reported:
Ubuntu Hardy Heron 8.04 x86_64
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5) Gecko/2008050509 Firefox/3.0b5
mozilla-acroread 8.1.2-0med
If I open a PDF in the browser (example: http://www.eff.org/files/filenode//EFF_ACTA_submission_032108_0.pdf ) it loads and displays without issue. Top shows it (as ld-linux.so.2) using 110MB of memory. If I browse away to a different page or close the tab, it starts consuming memory at a rate of 1MB/s. If I return back to the PDF, it spawns another instance of ld-linux.so.2 while the first continues to grow. I have to exit Firefox and kill ld-linux.so.2 else it will consume all available memory.
Another report:
http://ubuntuforums.org/showthread.php?t=754944
Terminal messages (repeats endlessly):
(acroread:8575): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(acroread:8575): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject'
(acroread:8575): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(acroread:8575): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject'
(acroread:8575): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(acroread:8575): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkObject'
(npviewer.bin:8374): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed
(npviewer.bin:8374): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
(npviewer.bin:8374): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(npviewer.bin:8374): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
(npviewer.bin:8374): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(npviewer.bin:8374): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed

Similar Messages

  • Editing in aperture is doing crazy things. I've read that it is memory leaks. Whats the cure?

    Aperture is doing crazy things while editing like leaving spots on faces when using skin smoothing tool among other things. Closing and reopening fixes it but how annoying. I've read that it is caused from memory leaks. What do I do to fix this?

    What is your Aperture version?
    And your MacOS X version?
    With Aperture 3 make sure you have the latest versions, Aperture 3.5.1 and OS 10.9.3.
    The memory leaks you are referring to occurred with MacOS 10.9.1 and onscreen proofing enabled.
    If yor versions are current, check your plug-ins for compatibility.

  • CVI dll to read XML file causes memory leak

    Hello,
    I am facing a memory leak issue when I execute a dll created using CVI to read a XML file.
    Each iteration of the step is taking around 200k of memory.
    Short description of the code:
    Basically I am using a function created in CVI to read from an XML file by tag which 2 attributes: command and the response;
    int GetCmdAndRsp(char XML_File[MAX_STR_SIZE], char tag[MAX_STR_SIZE], char Command[MAX_STR_SIZE], char Response[MAX_STR_SIZE], char ErrorDescription[MAX_STR_SIZE]) 
    inputs:  
    - XML_File_path;
    - tagToFind;
    ouputs:
    - Command;
    - Response;
    - Error;
    Example:
    XMLFile:
    <WriteParameter Command="0x9 %i %i %i %i %i" Response = "0x8 V %i %i %i %i"/>
    Execution:
    error = GetCmdAndRsp("c:\\temp\\ACS_Messages.xml" ,"WriteParameter", cmd, rsp, errStr) 
    output:
    error = 0
    cmd = "0x9 %i %i %i %i %i"
    rsp = "0x8 V %i %i %i %i"
    errStr = "Unkown Error"
    Everything is working correctly but I have this memory leak issue. Why am I having such memory consumption?? Is it a TestStand or CVI issue??
    Each iteration I am loading the file, reading the file and discarding the file.
    Attached you can find the CVI project, a TestStand sequence to test (ReadXML_test2.seq) and an example of a XML file I am using.
    Please help me here.
    Thaks in advance.
    Regards,
    Pedro Moreira
    Attachments:
    ReadXML_Prj.zip ‏1826 KB

    Pedro,
    When a TestStand step executes, its result will be stored by TestStand which will be later used for generating reports or logging data into database.
    You are looking at the memory (private bytes) when the sequence file has not finished execution. So, the memory you are looking at, includes the memory used by TestStand to store result of the step. The memory used for storing results will be de-allocated after finishing the sequence file execution.
    Hence, we dont know if there is actual memory leak or not. You should look at the memory, before and after executing sequence file instead of looking in between execution.
    Also, here are some pointers that will be helpful for checking memory leak in an application:
    1. TestStand is based on COM and uses BSTR in many function. BSTR caches the memory and because of the behavior, sometime you might get false notion of having memory leak. Hence, you need to use SetOaNoCache function OR set the OANOCACHE=1 environment variable to disable caching.
    2. Execute the sequence file atleast once before doing the actual memory leak test. The dry run will make sure all static variables are initialized before doing memory leak test.
    3. Make sure that the state of system or application is same when considering the Private bytes. Ex: Lets say ReportViewControl is not visible before you start executing sequence file. Then you note down the private bytes and then execute the sequence file. After finishing execution, make sure you close the ReportViewControl and then note down the private bytes once again to check if memory is leaked or not.
    4. If there exists memory leak as you specified, it is possible that the leak is either in TestStand, or in your code. Make sure that your code doesn't leak by creating a small standalone application (probably a console application) which calls your code.
    Detecting memory leaks in CVI is better explained in
    http://www.ni.com/white-paper/10785/en/
    http://www.ni.com/white-paper/7959/en/
    - Shashidhar

  • Memory Leak Java Plugin with Swing Applet

    Hi
    I experience the following problem and desperately need help on this. The Java Plugin (I use Version 1.3.1_02) seems to have a problem in printing Swing Applets.
    The problem can easily be reproduced (at least with NT):
    1) Start Internet Explorer or Netscape (I used 5.5/4.07)
    2) Launch the following demo swing applet
    http://java.sun.com/products/plugin/1.3.1_01a/demos/jfc/SwingSet2/SwingSet2Plugin.html
    3) Print the applet and observe (using task manager) the memory used by the browser process (the memory used by the process will increase every time you hit the print button but never decrease unless you shut down the browser)
    4) Print a couple of times (you may want to pause your print queue) and you will be able to crash your computer
    This seems to be the same bug reported with 4638742. However it says "in progress" for quite some time and I was wondering if some genious might know a work around for this.
    Cheers

    You might want to read an article about memory leaks in Java:
    http://www-106.ibm.com/developerworks/library/j-leaks/

  • Client-side Memory leak while executing PL/SQL and reading from a view

    Iam noticing memory leaks in OCCI while performing the following:
    Sample function()
    1. Obtain a connection
    2. Create a statement to execute a PL/SQL procedure
    3 Execute the statement created in step #2
    4. Terminate the statement created in step #2
    5. Create a statement to read from a view which was populated
    by executing stored procedure in step #3
    6. Execute the statement created in step #5
    7. Terminate the statement created in step #5
    8. Release the connection
    The PL/SQL populates a view with fixed 65,000 records for every execution. PL/SQL opens a cursor, loads 65000 records and populates the target view and closes the cursor at the end. If i invoke the above function it results in memory leak of 4M for every call. I tried several variants such as:
    1. Disabling statement caching
    2. Using setSQL instead of newly creating second SQL statement
    3. Obtaining two separate connections for these two activities (PL/SQL exec and View read)
    4. Breaking the sample function into two, one for each of these activities (PL/SQL exec and View read).
    All the combinations results in the same behaviour of 4M memory leak.
    Iam using Oracle 10g Client/Server 10.2.0.1.0.
    Is there any known limitations in this area?

    Yes. Iam closing the result set and terminating the statement.
    My program contains layers of inhouse wrapper classes, which will take some time for
    me to present it in pure OCCI calls, to be posted here for your understanding.
    After some more debugging, i found that if the connection level statement caching is set to
    0, the memory leak is much lower than before.
    Thanks.
    Message was edited by:
    user498920

  • Memory leak in Real-Time caused by VISA Read and Timed Loop data nodes? Doesn't make sense.

    Working with LV 8.2.1 real-time to develop a host of applications that monitor or emulate computers on RS-422 busses.   The following screen shots were taken from an application that monitors a 200Hz transmission.  After a few hours, the PXI station would crash with an awesome array of angry messages...most implying something about a loss of memory.  After much hair pulling and passing of the buck, my associate was able to discover while watching the available memory on the controller that memory loss was occurring with every loop containing a VISA read and error propogation using the data nodes (see Memory Leak.jpg).  He found that if he switched the error propogation to regular old-fashioned shift registers, then the available memory was rock-solid.  (a la No Memory Leak.jpg)
    Any ideas what could be causing this?  Do you see any problems with the way we code these sorts of loops?  We are always attempting to optimize the way we use memory on our time-critical applications and VISA reads and DAQmx Reads give us the most heartache as we are never able to preallocate memory for these VIs.  Any tips?
    Dan Marlow
    GDLS
    Solved!
    Go to Solution.
    Attachments:
    Memory Leak.JPG ‏136 KB
    No Memory Leak.JPG ‏137 KB

    Hi thisisnotadream,
    This problem has been reported, and you seem to be exactly reproducing the conditions required to see this problem. This was reported to R&D (# 134314) for further investigation. There are multiple possible workarounds, one of which is the one that you have already found of wiring the error directly into the loop. Other situations that result in no memory leak are:
    1.  If the bytes at port property node is not there and a read just happens in every iteration and resulting timeouts are ignored.
    2.  If the case structure is gone and just blindly check the bytes at port and read every iteration.
    3.  If the Timed Loop is turned into a While loop.
    Thanks for the feedback!
    Regards,Stephen S.
    National Instruments
    Applications Engineering

  • 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

  • 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...

  • How to determine memory leaks?

    I tried in XCODE, the RUN/ Start with Performance TOol / and tried out the various options. I was running my app and looking to see if it would report increasing memory use but it seemed to be looking at my total system (i was running under the simulator). In general what is the recommended procedure for determining memory leaks, which tool to use, and what tracing can i use?
    How does one look at the retain count of an object? are there system routines that have knonw leaks?

    You took the right path. Once instruments comes up select the Leaks tool. Turn off automatic leak detection. In your app, start off at some known state, do something, and come back to the known state and check for leaks. For instance start off in a view, do something that brings up another view then come back to the original view and check for leaks. Leaks will show you if you leaked. Since you took a very deterministic path then checked it should be straight forward to go to the code and find / fix the leaks. Leaks shows you where the code where the leak was generated.

  • Memory leak in JSpinner implementation (maybe others?)

    Hi,
    I am developing an application using Java and Swing, and have run into some problems with memory leaks. After examining the source code and making an example program (provided below), I can only come to the conclusion that there is a bug in the implementation of JSpinner in Sun Java 1.6.0_03.
    If one uses a custom model with the JSpinner, it attaches itself as a listener to the model. However, it never removes the listening connection, even if the model is changed. This causes the JSpinner to be kept in memory as long as the model exists, even if all other references to the component have been removed.
    An example program is available at http://eddie.dy.fi/~sampo/ModelTest.java . It is a simple swing program that has the JSpinner and two buttons, the first of which writes to stdout the listeners of the original model and the second changes the spinner model to a newly-created model. A sample output is below:
    Running on 1.6.0_03 from Sun Microsystems Inc.
    Listeners before connecting to JSpinner:
      Model value is 0, 0 listeners connected:
    Listeners after connecting to JSpinner:
      Model value is 0, 2 listeners connected:
      1: interface javax.swing.event.ChangeListener
      2: javax.swing.JSpinner$ModelListener@9971ad
    Listeners now:
      Model value is 8, 2 listeners connected:
      1: interface javax.swing.event.ChangeListener
      2: javax.swing.JSpinner$ModelListener@9971ad
    Changing spinner model.
    Listeners now:
      Model value is 8, 2 listeners connected:
      1: interface javax.swing.event.ChangeListener
      2: javax.swing.JSpinner$ModelListener@9971adThis shows that even though the model of the JSpinner has been changed, it still listens to the original model. I haven't looked at other components whether they retain connections to the old models as well.
    In my case, I have an adaptor-model which provides a SpinnerModel interface to the actual data. The adaptor is implemented so that it listens to the underlying model only when it itself is being listened to. If the JComponents using the model were to remove the listening connections, it, too, would be automatically garbage-collected. However, since JSpinner does not remove the connections, the adaptor also continues to listen to the underlying model, and neither can be garbage-collected.
    All in all, the listener-connections seem to be a very easy place to make memory leaks in Java and especially in Swing. However, as I see it, it would be a simple matter to make everything work automatically with one simple rule: Listen to the models only when necessary.
    If a component is hidden (or alternatively has no contact to a parent JFrame or equivalent), it does not need to listen to the model and should remove the connections. When the component is again set visible (or connected to a frame) it can re-add the connections and re-read the current model values just as it does when initializing the component. Similarly, any adaptor-models should listen to the underlying model only when it itself is being listened to.
    If the components were implemented in this way, one could simply remove a component from the frame and throw it away, and automatically any listener-connections will be removed and it can be garbage-collected. Similarly any adaptor-models are collected when they are no longer in use.
    Changing the API implementation in this way would not require any changes to applications, as the only thing that changes are the listener-connections. Currently used separate connection-removing methods should still work, though they would be unnecessary any more. The API would look exactly the same from the view of an application programmer, only that she would not need to care about remnant listening connections. (As far as I can tell, the current API specification would allow the API to be implemented as described above, but it should of course require it to be implemented in such a way.)
    Am I missing something, or is there some valid reason why the API is not implemented like this?
    PS. I'm new to these forums, so if there is a better place to post these reports, please tell me. Thanks.

    Another cognition: It's the following code, that causes the memory to be accumulated:
    obj = m_orb.resolve_initial_references("NameService");
    ctx = NamingContextExtHelper.narrow(obj);For the first 4 calls to this code the memory usage of the nameservice is unchanged. From the 5th to the 8th call, it's increased by approx. 10KB per call. And thenceforward (beginning with the 9th call) it's increasing by approx. 10MB.
    What's going wrong here?

  • T61 with memory leak on XP for driver battc.sys

    Hi
    I have an issue with XP where the battc.sys module that is part of Windows XP and responsible for the kernel side of monitoring the battery status. This module continually leaks memory until I have no more kernel paged resources left and programs start to fail on my laptop.
    I raised a support case for this with Microsoft and after some investigation and upgrading to the latest T61 power drivers that were released a few days ago on the Lenovo site, MS support told me it is a fault of the T61 and that I would need to disable Microsoft APCI support to stop this memory leak from occuring and to take the issue up with Lenovo.
    I have used the verifier tool to confirm that it is the Windows XP SP3 battc.sys memory module leaking.
    I am running the latest T61 drivers and fully patch with MS drivers on SP3.
    As MS have told me it is the fault of the T61 I am posting this issue here.
    Thanks
    Stephen

    It is memory available to the kernelwhich itself does not show under a process in task manager as far as I am aware (unles it is taken account as part of the system process).
    The best way to measure the available kernel memory space available is by using sysinternals procexp.
    You need to download procexp and also install the windows debugging tools from Microsoft. Then in procexp set the "Options > Configure Symbols : Debughlp.dll path" to the new debughlp.dll installed with your debu tools and set the symbols path to srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
    Then you can choose in procexp "View > System Information" and see the used and total paged and non-paged kernel memory space.
    poolmon helps monitor all the symbols that are taking up this memory and verifier lets you drill down to the exact module and the changes in memory for a module that is occuring.
    Here are two really good links on it
    http://blogs.msdn.com/ntdebugging/archive/2006/12/18/Understanding-Pool-Consumption-and-Event-ID_3A0...
    http://blogs.msdn.com/ntdebugging/archive/2008/05/08/tracking-down-mmst-paged-pool-usage.aspx
    In my poolmon i notice that Mmst and battc are taking alot of memory after my computer has been running for some time. Mmst being high is normal but battc should not continually be growing as it is which is why I raised the case to MS but they want verification it is not a Lenovo issue.

  • How do I report a major memory leak problem with Firefox 3.6.10 in WinXP?

    After I installed Firefox 3.6.9 on a WinXP desktop, I occasionally had minor memory leak problems, reflected by getting "out of virtual memory" messages. I upgraded to 3.6.10 when notified that it was available and that it supposedly fixed stability problems. Ever since then, whenever I use Firefox, it starts out quick as a flash, but very rapidly slows down to a crawl, and has twice brought my system to a halt. IE does not cause this, nor any other program I use, but the execution speed of all programs slows as badly as Firefox. If I knew where to get older versions, I would back up to 3.6.9 or earlier. The situation now prevents me from using Firefox much at all.

    Im running windows 7, Firefox 3.6.10 and before i updated to 3.6.10 my CPU never went above 10% with Firefox open. Now it can spike well above 50% and i have nothing different from when i had 3.6.9 to now when i have 3.6.10.
    There is no evidence for me to suggest one of the additions i have is causing it, its all pointing to Firefox itself and the last update.

  • How can I address a memory leak problem with Firefox?

    I have happily used Firefox for the past 7 years, and have rarely had difficulties. However, I am having some trouble now; Firefox (running 3.6.6) seems to have a memory leak on my machine. It's slower than what was discussed in other forum posts, but it still scales up slowly to multiple hundred MBs of Memory with very little CPU usage.
    I have tried disabling add-ons and extensions, but this does not stop the problem. I have cleared my cache and other stored data, but that also does not help. Has anyone experienced a similar problem that might be able to help?
    == This happened ==
    Every time Firefox opened
    == within last two weeks

    Hi reble0708,
    I have Java console disabled on my Firefox browser.Everything is working fine for me. There maybe other problem on your browser which is making PDF document faded and blurry. Can you post the link where you found the problem viewing the PDF document?
    Btw, you can go to ftp://ftp.mozilla.org/pub/firefox/releases/ and select the previous version of Firefox from the given options. There's no need to uninstall Firefox before you downgrade to the previous version of it.But before new installation, backup your Firefox profile folder.
    edit: replaced random unofficial download site link.

Maybe you are looking for