Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.
Firefox 44.0.2 - Memory Leakage Issue?
Firefox 44.0.2 seems to have a memory leakage problem on my Windows System 7 OS at current rev. Firefox crashed this morning when the memory exceeded 3.4 GB and a crash report was submitted. I then ran a simple test by bringing up a pair of web pages on Firefox and Google Chrome (same pages) with no activity on either browser after bringing up the webpages. An hour later the memory had substantially increased for Firefox (842,489 K - 1 process) and was continuing to increase while memory remained reasonably constant for Chrome (138,952 K - 4 processes).
Firefox updated to 45.0 and I am not able to replicate the problem anymore.Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0
All Replies (9)
You can type about:memory in the location tab to have a memory log. Are you able to reproduce the memory leak in safe mode?
Is this on a specific web page only ? (If so the address if it is a public page) Please let us have the Crash ID. Visit about:crashes. See details lower down. When you try safe mode does that prevent the issue and the Crash? If not please let us have a couple of Crash ID s from safe mode crashes.
Crash ID s
In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
- Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
- Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Firefox crashes - Troubleshoot, prevent and get help fixing crashes article.
Here is crash information: bp-b680fbbb-9e88-4389-bf1d-354512160304 3/3/2016 7:25 PM
I restarted Firefox in safe mode and have used Firefox for the past couple of hours. The memory usage continues to grow. At the moment it is around 1 GB. I saved an anonymized memory report, but am not seeing how I can attach it - failed as an image attachment. If/when Firefox crashes, I will send crash information and will attempt to attach the memory report at that time. Let me know if there is another way to send the memory report.
The actual memory log as displayed by about:memory is plain text, so small fragments of that may be copy and pasted into forum posts. The reports themselves are now gzip type files that this forum is unable to handle.
The about;memory will compare or diff report and that maybe very useful for showing where memory is disappearing to. If you see the issue on only one site it may be a problem with that site. What is the site and do you see the issue on other sites.
Try to give as an example a site with no video or Flash Player content. Ideally a site that is public, and has content that stays fairly constant.
The particular Crash report was not one that I personally found useful.
I was accessing ancestry.com when Firefox crashed. I have cleared my Firefox history, logged out of my Firefox account to stop synchronization with with my other PCs and brought up the main ancestry.com webpage. I let Firefox sit on this webpage for a couple of hours and will let you know what I observe later this afternoon.
The memory was 130 KB at 11:30 AM and is 153 KB at 9:45 PM using the webpage http://www.ancestry.com/ While the memory usage increased, it did not grow as it was before. I am going to turn synchronization back on and see how it looks tomorrow morning.
Sounds pretty normal at the moment. Nothing like your 3.4GB issue.
Firefox updated to 45.0 and I am not able to replicate the problem anymore.
Great. Thaanks for posting back. That sounds like a solution then, even if we never identified the cause.