Closed Bug 937290 Opened 11 years ago Closed 8 years ago

Firefox crashes consistently with 1MB jemalloc heap blocks

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
25 Branch
Platform:
x86_64
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: jgbittar, Unassigned)

Details

(Keywords: crash)

Attachments

(3 files)

Submitted Crash Reports.pdf list of reports submitted from about:crashes
31.41 KB, application/pdf
Details
memory report after 90 minutes of usage
968.44 KB, application/x-gzip
Details
1222014memory-report.json.gz
647.09 KB, application/x-gzip
Details 
Start Firefox and wait, eventually it crashes been running the same add on and extensions for months now.  This is either has to do with version 25 or windows 8/8.1 upgrade.
Many of these look like out-of-memory crashes of a sort I've been tracking for a while: we're leaking and running out of VM space but not running out of actual memory.

How soon after launching Firefox does it crash? Does the Firefox windows start looking strange before it crashes, such as turning black, not painting images properly, etc?

Could you try unchecking the following settings, and see whether that solves the issue?

Options -> Advanced -> General -> Use hardware acceleration when available

Once you've tried these, if you're interested in helping do some more in-depth debugging let me know and I'll link up some tools I've been using to figure this out.
Flags: needinfo?(jgbittar)
Ok hardware acceleration disabled as requested.  let me know what else should i do, unless we want to wait to see if this resolves the issue.
Flags: needinfo?(jgbittar)
Firefox crashed a few minutes after been up all morning without any issues here is the report id:

bp-e6a60f75-edc7-4a05-8d24-d28772131112
Firefox  crashed again about an hour ago, here is the report details. thanks

bp-0aad1a0c-34a8-4def-a3ad-ace812131113	11/13/2013	1:50 PM
Waiting to get some directions on the tools you mention before to continue trying to help correct this defect.
latest crashes report still the same problem any help will be appreciated


bp-7a0056d0-471e-4e78-86e8-ca9432131115	11/15/2013	4:37 PM
bp-d149df8c-192b-4f0e-af0b-7b0f72131115	11/15/2013	11:52 AM
bp-7662b877-4bdd-4f6a-98f5-ad5ec2131114	11/14/2013	2:42 PM
bp-8f994f9c-ab1f-4bfb-9a49-5f3682131114	11/14/2013	11:06 AM
Flags: needinfo?(benjamin)
redirect ni? to dmajor who's taking this whole VM-leaking mess.
Flags: needinfo?(benjamin) → needinfo?(dmajor)
Three of the six reports above are crashes in JS. They're not directly OOM crashes, but those low pointer values could certainly be consequences of a null allocation. Those three dumps had max free VA regions of 58MB, 17MB, and 17MB. Subjectively, !vadump took a long time to spew all the regions, which could point to fragmentation.

The other three reports were out of memory and have no minidump to go off of, but their OOM allocation sizes are 65K, 64, and 56 (bytes, not K!) even though memory is only 70-odd percent used.

jgbittar, I'm investigating similar issues on a lab machine. Until we better understand the source of these memory losses, I don't have any good recommendations. As a short-term workaround, you could try restarting the browser every couple of hours (I know that's not a pleasant solution).
Flags: needinfo?(dmajor)
these are the latest crashes, hope this helps, hopefully you will fix this soon restarting the browser every couple of hours is really not a clean option and i really would dislike to switch, opera would be the best candidate for me to start using but is there anything else that i can do to help?  i can not believe that this is not widespread, it seems to start after the latest 25 release.  thanks Jorge




bp-760bc7ad-3016-40a7-bf7c-913b32131119	11/19/2013	5:14 PM
bp-ee6219b8-7906-4192-a1ae-9973e2131118	11/18/2013	3:07 PM
bp-2dd0e7d3-ff38-4e35-a311-533872131118	11/18/2013	1:04 PM
bp-54fb0c4c-6fd7-46fe-8b24-6c4e22131116	11/16/2013	5:46 PM
bp-7a0056d0-471e-4e78-86e8-ca9432131115	11/15/2013	4:37 PM
bp-d149df8c-192b-4f0e-af0b-7b0f72131115	11/15/2013	11:52 AM
Severity: normal → critical
Keywords: crash
Are you still seeing crashes in version 26? This release has better crash reporting in low-memory situations, so maybe it can help us get a better understanding of the issue.
Flags: needinfo?(jgbittar)
these are the 3 last crashes can't tell if they are related to the same issue.
bp-e81a2cd2-4e2e-4663-a1ae-99be02140115	1/15/2014	1:14 PM
bp-9130606b-a794-4dbe-9f69-4754c2131216	12/16/2013	4:33 PM
bp-f4b396be-482a-4dcc-823f-d97622131216	12/16/2013	1:21 PM
bp-3508c8f9-49db-4a37-a67c-2ee932131216	12/16/2013	11:24 AM
bp-cdc24242-c48d-4d44-b68c-5c8ee2131214	12/14/2013	5:59 PM
Flags: needinfo?(jgbittar)
 mozalloc_abort(char const* const) | NS_DebugBreak | nsAString_internal::Assign(wchar_t const*, unsigned int)
bp-9130606b-a794-4dbe-9f69-4754c2131216

 JS_GetCompartmentPrincipals(JSCompartment*) 
bp-f4b396be-482a-4dcc-823f-d97622131216

 mozalloc_abort(char const* const) | NS_DebugBreak | nsPresArena::Allocate(unsigned int, unsigned int) 
bp-3508c8f9-49db-4a37-a67c-2ee932131216

 mozilla::dom::UnwrapDOMObject<nsISupports>(JSObject*) 
bp-cdc24242-c48d-4d44-b68c-5c8ee2131214
The first and third crashes from comment 12 are explicitly OOM crashes. The second and fourth are a little fuzzier, I didn't dig too deep.
These crash reports consistently have 3000+ regions of size 1MB, presumably jemalloc heap blocks. I'm curious what kind of objects these are.

jgbittar, could you save a report from about:memory after about 90 minutes of usage?
as requested here is the memory report let me know if you need anything else. thanks jorge
Andrew, can you help me read this memory report? It seems odd that there are hundreds of entries for about:blank under window-objects. Does that indicate that something is holding on to every tab ever created?
Flags: needinfo?(continuation)
There are a lot, but maybe if there are a lot of unrestored windows you'd see that.

Nothing in there really stands out to me, except for the three 16MB strings zone(0x6044000).  I'm guessing they are related to a SessionManager addon.  If it is leaking 16MB strings, that'll add up...
Flags: needinfo?(continuation)
the latest crashes with the memory report today has been a trying day

bp-028f2bb6-d4af-4c38-b761-3a26a2140122	1/22/2014	3:01 PM
bp-e3dc42a9-29a9-40fa-a341-03cc02140122	1/22/2014	11:15 AM
bp-0045203a-cfbf-451d-84b4-165c02140122	1/22/2014	10:45 AM
d76f88b8-86d4-4326-8c5b-6bf905f60ed7	1/20/2014	1:13 PM
622bdf43-43c1-4128-bb35-cb6ecc168a70	1/20/2014	1:13 PM
Nothing in particular sticks out from the memory reports. It's almost like something is just holding on to everything in sight. There are a number of addons installed, maybe one of them could be involved.

Jorge, do you still crash if you run the browser in safe mode?
I'm experiencing this bastard too. Since mid-2013/FF25, currently on 27.0.1. Typically it slows down, starts to leak memory, may do some odd graphics things, then eventually hangs and sits there leaking RAM until about 3.5GB is reached, at which point it crashes. sample crash: https://crash-stats.mozilla.com/report/index/47945de7-0e28-4ca9-b343-1c2aa2140310

worst was 16th october 2013 - 7 crashes, including 4 in an hour.
PS, does Jorge use TabGroups Manager (I do, and that might keep track of large numbers of tabs and possibly fail to free resources?)
I use tabmix plus
I have 32.0.3 on Windows 7 SP1 Enterprise and it has been crashing a lot... I don't know why... I've also submitted the crash reports to Mozilla as well... When I'm actively using it throughout the day it's fine, but when it goes idle it seems to crash...
poobsiab, your most recent crash report was caused by this issue: https://support.mozilla.org/en-US/questions/1016561. The Symantec developer in bug 1075213 might be interested in hearing from you.

(For anyone else reading, comment 24 is unrelated to the OOMs discussed in this bug)
jgbittar, I don't see any crashes for your email address crash-stats since 2014-08-01.  
How did you solve your crash issue?

(In reply to Wayne Mery (:wsmwk) from comment #12)
>  mozilla::dom::UnwrapDOMObject<nsISupports>(JSObject*) 
> bp-cdc24242-c48d-4d44-b68c-5c8ee2131214

 0 	xul.dll	mozilla::dom::UnwrapDOMObject<nsISupports>(JSObject*)	obj-firefox/dist/include/mozilla/dom/BindingUtils.h
1 	xul.dll	SuspectDOMExpandos	js/xpconnect/src/XPCWrappedNativeScope.cpp
2 	xul.dll	XPCWrappedNativeScope::SuspectAllWrappers(XPCJSRuntime*, nsCycleCollectionNoteRootCallback&)	js/xpconnect/src/XPCWrappedNativeScope.cpp
Flags: needinfo?(jgbittar)
Summary: Firefox crashes consistently → Firefox crashes consistently with 1MB jemalloc heap blocks
(In reply to Wayne Mery (:wsmwk) from comment #26)
> jgbittar, I don't see any crashes for your email address crash-stats since
> 2014-08-01.  
> How did you solve your crash issue?
> 
> (In reply to Wayne Mery (:wsmwk) from comment #12)
> >  mozilla::dom::UnwrapDOMObject<nsISupports>(JSObject*) 
> > bp-cdc24242-c48d-4d44-b68c-5c8ee2131214
> 
>  0 	xul.dll	mozilla::dom::UnwrapDOMObject<nsISupports>(JSObject*)
> obj-firefox/dist/include/mozilla/dom/BindingUtils.h
> 1 	xul.dll	SuspectDOMExpandos	js/xpconnect/src/XPCWrappedNativeScope.cpp
> 2 	xul.dll	XPCWrappedNativeScope::SuspectAllWrappers(XPCJSRuntime*,
> nsCycleCollectionNoteRootCallback&)
> js/xpconnect/src/XPCWrappedNativeScope.cpp

Wayne unfortunately i use Firefox sporadically i do keep it to the latest version and i use as a reference when something goes wrong with my main browser, palemoon which is my browser of choice.  I have over 350 tabs at the time that palemoon has no trouble loading, the latest version of Firefox takes forever to load them, but it does load them, it used to crash on previous versions, every time mozilla releases a version i do check it.  if there is anything that you or your teams wants me to check let me know i be happy to do so.  have a great new years!!! thanks jorge
Flags: needinfo?(jgbittar)
(In reply to dmajor (away) from comment #19)
> Nothing in particular sticks out from the memory reports. It's almost like
> something is just holding on to everything in sight. There are a number of
> addons installed, maybe one of them could be involved.
> 
> Jorge, do you still crash if you run the browser in safe mode?

(In reply to jgbittar from comment #23)
> I use tabmix plus

Not sure that's the info dmajor was hoping for :)
If you still see this without tabmix plus please reopen the bug
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
I have not use Firefox in a while will check an update this tread, i use palemoon 64 bit no issues ever with 450+ tabs thanks jorge
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: