X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

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

Firefox 26 on OS X 10.9.1 still has huge memory usuage (leak) which leads to crash

Kuphostiwe

Hi, The subject is sort of self explanatory but for the last few months (not sure exactly when) i have had regular Firefox crashes, it seems to happen when i'm out of memory and FF has used all the available RAM. I have a MBP with i7 and 8gig of RAM using the latest OSX 10.9.1 and latest FF 26. I always keep up to date with the software. Usually i have about 20 or so tabs open and go back and forth between these. I have googled and read allot on this topic and most people recommend starting in safe mode, without add-ons , creating clean profile etc and i have done these but slowly i get back into the same issue even after a clean profile.... It seems for every FF update the memory usage increases....back in the day FF was extremely fast and efficient. Or maybe latest FF just wants to remember so much and save just to much old information which leads to these ridiculous amount of memory usage, i tend to go over 3-4gig RAM after half a day alone before it crashes and all my tabs are lost which is extremely frustrating. Is there a way to limit the memory usage? Only helpful tips i have found so far that seems to remove allot of garbage from the cache and the footprint is going to about:memory and run the "minimize memory usage", this has been working great and so far after 2-3 hours its steady on 900meg (more or less) with 16 tabs open. Isnt this something FF needs to do regularly to get rid of old stuff ? i saw youtube and many other old stuff in the cache which i was not using and caused FF to go over 2 gig or so before i run this so why isnt this automated? as a user i shouldnt need to care about such thins really. I also used Safari for a few weeks with same amount of tabs and it never goes over 800-900 meg. I really hope you guys can explain and give me some tips as to how to limit the memory usage of FF and not the regular make a clean profile and generic tips. I really think the problem is FF and nothing else. I done extensive testing here and i'm using just a few add-ons Adblock plus All in one Gestures Swedish dictioanary Downloadhelper Screengrab Download Statusbar

Sorry if i sound irritated but having to lose my tabs daily and being forced to bookmark my tabs constantly just in case FF crashes has been bugging me for a while now and i'm on the verge to switch browser but frankly there is no other browser as good as FF (offering same amount of plugins/add-ons) so i badly want to use FF if possible.

If you need any more info let me know.

Cheers

Hi, The subject is sort of self explanatory but for the last few months (not sure exactly when) i have had regular Firefox crashes, it seems to happen when i'm out of memory and FF has used all the available RAM. I have a MBP with i7 and 8gig of RAM using the latest OSX 10.9.1 and latest FF 26. I always keep up to date with the software. Usually i have about 20 or so tabs open and go back and forth between these. I have googled and read allot on this topic and most people recommend starting in safe mode, without add-ons , creating clean profile etc and i have done these but slowly i get back into the same issue even after a clean profile.... It seems for every FF update the memory usage increases....back in the day FF was extremely fast and efficient. Or maybe latest FF just wants to remember so much and save just to much old information which leads to these ridiculous amount of memory usage, i tend to go over 3-4gig RAM after half a day alone before it crashes and all my tabs are lost which is extremely frustrating. Is there a way to limit the memory usage? Only helpful tips i have found so far that seems to remove allot of garbage from the cache and the footprint is going to about:memory and run the "minimize memory usage", this has been working great and so far after 2-3 hours its steady on 900meg (more or less) with 16 tabs open. Isnt this something FF needs to do regularly to get rid of old stuff ? i saw youtube and many other old stuff in the cache which i was not using and caused FF to go over 2 gig or so before i run this so why isnt this automated? as a user i shouldnt need to care about such thins really. I also used Safari for a few weeks with same amount of tabs and it never goes over 800-900 meg. I really hope you guys can explain and give me some tips as to how to limit the memory usage of FF and not the regular make a clean profile and generic tips. I really think the problem is FF and nothing else. I done extensive testing here and i'm using just a few add-ons Adblock plus All in one Gestures Swedish dictioanary Downloadhelper Screengrab Download Statusbar Sorry if i sound irritated but having to lose my tabs daily and being forced to bookmark my tabs constantly just in case FF crashes has been bugging me for a while now and i'm on the verge to switch browser but frankly there is no other browser as good as FF (offering same amount of plugins/add-ons) so i badly want to use FF if possible. If you need any more info let me know. Cheers

Okulungisiwe ngu vampyren

Isisombululo esikhethiwe

Thanks MacKnickKnack,

Glad to see that although the problem turned out to be a Firefox bug that it is one that has been fixed in Firefox 28. So now no problems if running Firefox 28 ( Currently Beta )

* Bug 937878 - Extremely high layer memory usage on Mac when browser windows are minimized
Funda le mpendulo ngokuhambisana nalesi sihloko 0

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site.
  • Provides information about the default web browser
  • Shockwave Flash 11.9 r900
  • Displays Java applet content, or a placeholder if Java is not installed.
  • Microsoft Office for Mac SharePoint Browser Plug-in
  • Microsoft Lync 2010 Meeting Join Plug-in

Isisebenziso

  • Firefox 26.0
  • Umsebenzisi oyi-ejenti: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:26.0) Gecko/20100101 Firefox/26.0
  • I-URL Yokweseka: https://support.mozilla.org/1/firefox/26.0/Darwin/en-US/

Izandiso

  • Adblock Plus 2.4 ({d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d})
  • All-in-One Gestures 0.26 ({8b86149f-01fb-4842-9dd8-4d7eb02fd055})
  • Den stora svenska ordlistan 2.21 (sv@dsso.se)
  • DownloadHelper 4.9.21 ({b9db16a4-6edc-47ec-a1f4-b86292ed211d})
  • Screengrab (fix version) 0.97.18c ({02450914-cdd9-410f-b1da-db004e18c671})
  • Svensk ordlista 1.49 (sv@dictionaries.addons.mozilla.org)
  • Troubleshooter 1.1a (troubleshooter@mozilla.org)
  • Download Statusbar 0.9.10 ({D4DD63FA-01E4-46a7-B6B1-EDAB7D6AD389}) (Akusebenzi)

I-Javascript

  • incrementalGCEnabled: True

Imidwebo

  • adapterDescription:
  • adapterDeviceID: 0x 46
  • adapterDrivers:
  • adapterRAM:
  • adapterVendorID: 0x8086
  • driverDate:
  • driverVersion:
  • info: {u'AzureContentBackend': u'quartz', u'AzureCanvasBackend': u'quartz', u'AzureFallbackCanvasBackend': u'none', u'AzureSkiaAccelerated': 0}
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • webglRenderer: NVIDIA Corporation -- NVIDIA GeForce GT 330M OpenGL Engine
  • windowLayerManagerRemote: True
  • windowLayerManagerType: OpenGL

Okuthandwayo Okulungisiwe

  • accessibility.typeaheadfind: True
  • 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.display.use_system_colors: True
  • browser.history_expire_days.mirror: 180
  • browser.places.importBookmarksHTML: False
  • browser.places.smartBookmarksVersion: 4
  • browser.privatebrowsing.dont_prompt_on_enter: True
  • browser.sessionstore.resume_from_crash: False
  • browser.sessionstore.upgradeBackup.latestBuildID: 20131205075310
  • browser.startup.homepage_override.buildID: 20131205075310
  • browser.startup.homepage_override.mstone: 26.0
  • browser.tabs.warnOnClose: False
  • browser.tabs.warnOnOpen: False
  • dom.max_chrome_script_run_time: 40
  • dom.max_script_run_time: 0
  • dom.mozApps.used: True
  • extensions.lastAppVersion: 26.0
  • general.autoScroll: False
  • network.cookie.prefsMigrated: True
  • places.database.lastMaintenance: 1388192360
  • places.history.expiration.transient_current_max_pages: 104858
  • places.history.expiration.transient_optimal_database_size: 166429982
  • places.last_vacuum: 1296322912
  • plugin.disable_full_page_plugin_for_types: application/pdf
  • plugin.importedState: True
  • privacy.cpd.cookies: False
  • privacy.cpd.extensions-dta: True
  • privacy.cpd.extensions-tabmix: False
  • privacy.cpd.formdata: False
  • privacy.cpd.sessions: False
  • privacy.donottrackheader.enabled: True
  • privacy.item.extensions-dta: True
  • privacy.sanitize.migrateFx3Prefs: True
  • privacy.sanitize.timeSpan: 0
  • security.warn_viewing_mixed: False
  • storage.vacuum.last.index: 1
  • storage.vacuum.last.places.sqlite: 1387013153

Misc

  • Umsebenzisi JS: Cha
  • Ukufinyeleleka: Cha
guigs 1072 izisombululo 11697 izimpendulo
Kuphostiwe

Hi MacKnickKnack,

The beta is coming to the official release this week. If you continue to see this issue in the new version please start a thread with a reference to this bug.

I will marked the bug as resolved for this thread.

Hi MacKnickKnack, The beta is coming to the official release this week. If you continue to see this issue in the new version please start a thread with a reference to this bug. I will marked the bug as resolved for this thread.