Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Learn More

Firefox 27 memory leak (/questions/978195)

  • 2 odpovede
  • 34 má tento problém
  • 17 zobrazení
  • Posledná odpoveď od guigs

more options

I already did this, sorry , but now I include the automated information..... More than 6GB in 3 hours (MacOSX 10.7.5, 16Gb RAM)



(No time personally to look at this but, I have tagged it as escalate)

I already did this, sorry , but now I include the automated information..... More than 6GB in 3 hours (MacOSX 10.7.5, 16Gb RAM) ------ (No time personally to look at this but, I have tagged it as escalate)

Upravil(a) John99 dňa

Všetky odpovede (2)

more options

I will make a quick comment, but am unlikely to get back to this again before the weekend.

First do not think we are ignoring this or saying it is not a problem. It is a case of it is something often difficult to pin down and must initially be checked and compared with Firefox in a clean configuration, and using memory figures from the Firefox's reporter about:memory.

If you can ramp up memory usage to 6GB in only 3 hours at least it should be relatively easy to demonstrate whether or not something prevents that from happening.

As a test please

  • Make an new additional Firefox Profile,
  • Run Firefox in Firefox's safe mode
  • With all plugins disabled
  • Look at memory use by using about:memory
  • Browse for a few hours, has the problem now disappeared ?

Instructions and discussions about this can be seen in thread

  • Firefox 26 on OS X 10.9.1 still has huge memory usuage (leak) which leads to crash /questions/981674
  • Thread mentioned in tile is
    Firefox 25 still has memory leaks /questions/978195
more options

Hey agm_csic0,

Thank you for posting your question, and thank you John99 for summing it up^ The resources that are being used will depend on the processes that are running. In the about:memory, run a quick report to see what is taking up the most memory, please post back with any errors or issues that you continue to notice after the changes suggested above.

We are happy to troubleshoot from there as well.