Closed
Bug 1185289
Opened 9 years ago
Closed 9 years ago
Mozilla 39.0 Crash Issue
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1159751
People
(Reporter: chahal.asia05, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150630154324
Steps to reproduce:
Hello,
I recently updated my laptop browser to 39.0
Actual results:
But after update successfully installed.
My mozilla started crashing immediately.
I thought something went wrong. I removed mozilla and all its relevant directories. + App folder as well from app data section as i am using Windows 7.
After complete removal i reinstalled it and facing same issue. its been since mozilla 39.0 update came i am facing this issue.
Next day i went to my office and my office all employees started complaining the same issue.
Since they updated their mozilla whenever they open mozilla its eating whole of the memory.
Its like i have 4GB ram in my laptop. In few minutes its eating whole 4GB ram even if i have opened 1 tab only still eating whole ram.
Same issue my office employees also facing.
On getting same issues everywhere i came on a point there is some serious bug in this update which is causing this issue.
I tried to disable the addons as well but still facing same issue.
Please fix this bug
Expected results:
It should never eat that much ram on even opening a single tab. Its eating whole ram. in my office i have 32GB ram server your mozilla since i updated my office server crashed once as my tech guy opened the mozilla and he forget to close it.
But it was only 1 tab which he left opened. This is very serious issue resolve this
Comment 1•9 years ago
|
||
Please go to about:crashes and post some URLs from crashlog reports,
and when you're having memory leaks go to about:memory and "Measure and save" memory report and attach it here.
Flags: needinfo?(chahal.asia05)
https://crash-stats.mozilla.com/report/index/e47e342f-f237-4157-992a-da9b22150719
https://crash-stats.mozilla.com/report/index/558ec7c4-518d-428a-ab91-2d78b2150714
https://crash-stats.mozilla.com/report/index/8df03784-f211-46c0-b916-3e4952150714
https://crash-stats.mozilla.com/report/index/a6671828-f262-422c-a5f0-446582150714
https://crash-stats.mozilla.com/report/index/561e197c-2899-4b39-84f3-86ea52150714
https://crash-stats.mozilla.com/report/index/bb200bbe-938c-4142-a96f-1c4bd2150719
Here are the URL's
These are the urls from my laptop same issue my employees also experiencing in office too.
Flags: needinfo?(chahal.asia05)
Comment 3•9 years ago
|
||
Most of your crashes leads to bug #1185289, so I'm marking this bug as duplicate of it.
One of the crashes leads to bug #1171970 which is fixed on Firefox 41. I requested uplift, so maybe it will be fixed in Firefox 40.
Other crash with crashlog report signature like this [@ OOM | small ] is simply out of memory error and is being tracked in various bugs per bug #1034254 Comment 3 and #1034254 Comment 5.
Workaround probably for your main issue for time being is disabling WARP. To do that go to about:config and set "layers.d3d11.disable-warp" preference to "true" value. You can also disable whole hardware acceleration, if the workaround won't be helping. To do that go to Advanced Firefox options under General tab and uncheck "Use hardware acceleration when available".
I would also recommending using Firefox ESR in the mass deployments.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•