1056230 - Firefox 31 crashes [@ OOM | small ] VERY frequently in mozalloc_handle_oom() in mozalloc_oom.cpp#L50

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[Piyush Soni]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140716183446

Steps to reproduce:

I have many tabs open most of the time. Just using standard release build of Firefix 31 and seeing many crashes. It's very difficult to single out one page which might be causing a crash. The steps are: 
1) Just open Firefox 31 and surf as a heavy user, open all sorts of websites. 
2) See a crash in mozalloc_handle_oom() in the file mozalloc_oom.cpp at line 50 ( mozalloc_abort(oomMsg);) 

Here are some of the crash report ids I submitted when it crashed: 
bp-a2b3dead-bd09-4c74-8ed9-d726c2140820
bp-0baf8e1f-5071-4d05-b9ec-683482140820
bp-8fddf1e9-3252-4130-bc11-aa5772140820
bp-6ed07282-eaf1-423c-bcd4-7c2912140820
bp-0258f05c-87cf-4da0-b839-24c102140820
bp-67108108-e91b-4efe-b16c-38e552140820
bp-487798cf-c09e-4cd5-b5e4-4aaaf2140820


Actual results:

Firefox crashes frequently with showing the Crash Reporter dialog. When you restart and 'Restore the session', the crash occurs again in a few minutes. Only if you close all pages together and start a new session it doesn't happen for some time (to a couple of days)


Expected results:

It shouldn't have crashed. I don't know what this crash is related to. I have Quadro 600 Graphics card, if that helps.

Comment 1

[Loic]

Can you monitor the memory use of Firefox before it crashes? (in about:memory save a log)
In addition, you have many add-ons, maybe one of them is the culprit.

Comment 2

[Piyush Soni]

Hi, 
Yes, I was about to add that information, because it's odd. As soon as I restarted Firefox, it was going quickly to 3 GB (I could see the quickly increasing the memory usage in the Windows TaskManager). And soon after its memory usage reached 3 GB, it crashes because probably it cannot allocate any more memory. 

Yes, I have many add-ons. But the problem is, Firefox doesn't make it easy at all to find out the misbehaving add-ons (I had even logged a bug about this long back: bug 621607). How do I know which one is causing this? I can see the memory usage increasing, but I am sure it's possible that Firefox can include a tool to find out who is requesting Memory Allocation at that fast rate, and probably not freeing it. The standard suggested ways - restarting in Safe mode (/ or add ons disabled) is not at all helpful - It's either ALL add-ons, or NONE enabled. How am I supposed to find out which? Thanks ...

Comment 3

[:Gijs (he/him)]

(In reply to Piyush Soni from comment #2)
> Hi, 
> Yes, I was about to add that information, because it's odd. As soon as I
> restarted Firefox, it was going quickly to 3 GB (I could see the quickly
> increasing the memory usage in the Windows TaskManager). And soon after its
> memory usage reached 3 GB, it crashes because probably it cannot allocate
> any more memory. 
> 
> Yes, I have many add-ons. But the problem is, Firefox doesn't make it easy
> at all to find out the misbehaving add-ons (I had even logged a bug about
> this long back: bug 621607). How do I know which one is causing this? I can
> see the memory usage increasing, but I am sure it's possible that Firefox
> can include a tool to find out who is requesting Memory Allocation at that
> fast rate, and probably not freeing it. The standard suggested ways -
> restarting in Safe mode (/ or add ons disabled) is not at all helpful - It's
> either ALL add-ons, or NONE enabled. How am I supposed to find out which?
> Thanks ...

It's possible about:memory can tell you (Click "Measure"). You can also save a log from there and attach it here so we can have a look.

Otherwise, in terms of diagnosing, you could disable half your add-ons from about:addons yourself and restart, and then "bisect" (so keep disabling halves) until you find the culprit.

Comment 4

[Wayne Mery (:wsmwk)]

See comment 3.
Also, you might try Help | troublshooting | Reset

Comment 5

[Phoenix]

Resolved per whiteboard