X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox 27 memory leak (/questions/978195)

Kuphostiwe

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)

Okulungisiwe ngu John99

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Version 5.1.4.17398
  • Google Talk Plugin Video Accelerator version:0.1.44.29
  • DivX VOD Helper Plug-in
  • DivX Web Player version 3.1.0.13
  • QuickTime Plug-in permite visualizar una amplia variedad de material multimedia en páginas web. Para más información, visite la web QuickTime.
  • Java Plug-In 2 for NPAPI Browsers
  • Microsoft Office for Mac SharePoint Browser Plug-in
  • Shockwave Flash 11.9 r900
  • The Flip4Mac WMV Plugin allows you to view Windows Media content using QuickTime.
  • Plugin that detects installed Citrix Online products (visit www.citrixonline.com).

Isisebenziso

  • Firefox 27.0.1
  • Umsebenzisi oyi-ejenti: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:27.0) Gecko/20100101 Firefox/27.0
  • I-URL Yokweseka: https://support.mozilla.org/1/firefox/27.0.1/Darwin/es-ES/

Izandiso

  • Troubleshooter 1.1a (troubleshooter@mozilla.org)
  • Adobe Acrobat - Create PDF 1.2 (web2pdfextension@web2pdf.adobedotcom) (Akusebenzi)

I-Javascript

  • incrementalGCEnabled: True

Imidwebo

  • adapterDescription:
  • adapterDeviceID: 0x6720
  • adapterDrivers:
  • adapterRAM:
  • adapterVendorID: 0x1002
  • driverDate:
  • driverVersion:
  • info: {u'AzureContentBackend': u'quartz', u'AzureCanvasBackend': u'quartz', u'AzureFallbackCanvasBackend': u'none', u'AzureSkiaAccelerated': 0}
  • numAcceleratedWindows: 2
  • numTotalWindows: 2
  • webglRenderer: ATI Technologies Inc. -- ATI Radeon HD 6970M OpenGL Engine
  • windowLayerManagerRemote: True
  • windowLayerManagerType: OpenGL

Okuthandwayo Okulungisiwe

  • accessibility.typeaheadfind.flashBar: 0
  • browser.cache.disk.capacity: 358400
  • browser.cache.disk.smart_size.first_run: False
  • browser.cache.disk.smart_size.use_old_max: False
  • browser.cache.disk.smart_size_cached_value: 358400
  • browser.places.smartBookmarksVersion: 4
  • browser.sessionstore.upgradeBackup.latestBuildID: 20140212131424
  • browser.startup.homepage: http://www.imm-cnm.csic.es/magnetoplasmonics
  • browser.startup.homepage_override.buildID: 20140212131424
  • browser.startup.homepage_override.mstone: 27.0.1
  • dom.mozApps.used: True
  • dom.w3c_touch_events.expose: False
  • extensions.lastAppVersion: 27.0.1
  • font.internaluseonly.changed: True
  • gfx.blacklist.direct2d: 3
  • gfx.blacklist.layers.direct3d9: 3
  • gfx.blacklist.webgl.msaa: 4
  • network.cookie.prefsMigrated: True
  • places.database.lastMaintenance: 1393320643
  • places.history.expiration.transient_current_max_pages: 104858
  • plugin.disable_full_page_plugin_for_types: application/vnd.fdf,application/pdf
  • plugin.importedState: True
  • plugin.state.adobepdfviewernpapi: 0
  • privacy.sanitize.migrateFx3Prefs: True
  • security.warn_viewing_mixed: False
  • storage.vacuum.last.index: 1
  • storage.vacuum.last.places.sqlite: 1392631020

Misc

  • Umsebenzisi JS: Cha
  • Ukufinyeleleka: Cha
John99 971 izisombululo 13138 izimpendulo
Kuphostiwe

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
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 <br />''Firefox 25 still has memory leaks'' [/questions/978195]
guigs 1072 izisombululo 11697 izimpendulo
Kuphostiwe

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.

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.