658830 - Firefox 5 Beta with Firebug 1.8a2 crashes with a window with 570 tabs open. [@ AllocateArena<JSObject> ]

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[kten50]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0

I installed Firefox 5 Beta on my machine and found that Firebug 1.7.1 was listed as incompatible. I searched and found that Firebug 1.8a2 was for Firefox 5 Beta. When I installed Firebug 1.8a2, my copy of Firefox 5 Beta crashed and I had to access "safe mode" from the run box in Windows 7 to go in and uninstall Firebug 1.8a2 to get Firefox 5 Beta working again. Went into safe mode and looked through websites in window. I closed out 482 tabs that I read but forgot to close. I've been using 'browser.sessionstore.max_concurrent_tabs' set to '0' to only load the active tab in each window. Retired with old profile with both 'development window' and cleaned up 'web surfing window' (with only 88 current tabs I keep open for Folding@Home status/Steam/GOG.com/New Egg/PHP.net/Reddit/Beta News/etc.) open and Firebug 1.8a2 and profile worked again.

Reproducible: Always

Steps to Reproduce:
1.Install Firefox 5 Beta over Firefox 4.0.1.
2.Everything opens fine and runs fine.
3.Upgrade Firebug 1.7.1 to Firebug 1.8a2.
4.Restart Firefox 5 Beta.

6.Restart Firefox 5 Beta in 'safe mode'.
7.Either disable or uninstall Firebug 1.8a2.
8.Firefox 5 Beta works.

Actual Results:  
Firefox 5 Beta crashes.

Expected Results:  
Firefox 5 Beta with lots of tabs open should work irregardless Firebug version.

I don't know why Firefox 4 w/ Firebug 1.7.1 (along with the Firefox 4 Betas w/ Firebug 1.7betas) and Firefox 5 Beta w/o Firebug 1.8a2 didn't crash opening but not loading a window with 570 tabs and why Firefox 5 Beta w/ Firebug 1.8a2 did crash under those same conditions. I realize that I'm an edge case as far as tab usage and hoarding goes. Still, this is the first time as someone who uses Firefox + Firebug, that I have encountered a problem where upgrading Firebug crashes a Firefox window with too many tabs.

I complained at <a href="https://groups.google.com/group/firebug/browse_thread/thread/b1e9af00beaaaa86">Google Groups-Firebug: "Firebug 1.8a2"</a> and was told to file bug as the problem probably was a Firefox problem and not a Firebug problem.

Being as you asked for stack traces, here are the following crash reports that 'about:crashes' list:
bp-67550c8c-ac07-4ee1-aace-7e0992110521 5/21/2011 5:04 PM
bp-b8e35936-b3c8-45ba-8c5f-57c7c2110521 5/21/2011 5:03 PM
bp-a6298b9a-3c74-45aa-8b4e-a05172110521 5/21/2011 5:02 PM
bp-848a947d-2d6c-439b-afd1-4e6722110521 5/21/2011 3:23 PM
bp-b96b031f-1d00-4cc1-a6ab-4e05e2110521 5/21/2011 3:23 PM
bp-6823c068-76cc-455c-9dd4-106732110521 5/21/2011 3:22 AM
bp-f0b82ccd-8fbc-4078-81b8-64f1d2110521 5/21/2011 2:48 AM

Comment 1

[Thomas Ahlblom]

0 	mozjs.dll 	AllocateArena<JSObject> 	js/src/jsgc.cpp:490
1 	mozjs.dll 	RefillTypedFreeList<JSObject> 	js/src/jsgc.cpp:1171
2 	mozjs.dll 	RefillFinalizableFreeList 	js/src/jsgc.cpp:1190
3 	mozjs.dll 	JS_NewGlobalObject 	js/src/jsapi.cpp:3054
4 	mozjs.dll 	JS_NewCompartmentAndGlobalObject 	js/src/jsapi.cpp:3100
5 	xul.dll 	CreateNewCompartment 	js/src/xpconnect/src/nsXPConnect.cpp:1018
6 	xul.dll 	xpc_CreateGlobalObject 	js/src/xpconnect/src/nsXPConnect.cpp:1056
7 	xul.dll 	nsXPConnect::InitClassesWithNewWrappedGlobal 	js/src/xpconnect/src/nsXPConnect.cpp:1219
8 	xul.dll 	nsJSContext::CreateNativeGlobalForInner 	dom/base/nsJSEnvironment.cpp:2243
9 	xul.dll 	nsGlobalWindow::SetNewDocument 	dom/base/nsGlobalWindow.cpp:2019
10 	xul.dll 	DocumentViewerImpl::InitInternal 	layout/base/nsDocumentViewer.cpp:980
11 	xul.dll 	DocumentViewerImpl::Init 	layout/base/nsDocumentViewer.cpp:709
12 	xul.dll 	nsDocShell::SetupNewViewer 	docshell/base/nsDocShell.cpp:7696
13 	xul.dll 	nsDocShell::Embed 	docshell/base/nsDocShell.cpp:5741
14 	xul.dll 	nsDocShell::CreateAboutBlankContentViewer 	docshell/base/nsDocShell.cpp:6516
15 	xul.dll 	nsDocShell::EnsureContentViewer 	docshell/base/nsDocShell.cpp:6422
16 	xul.dll 	nsDocShell::GetInterface 	docshell/base/nsDocShell.cpp:893
17 	xul.dll 	xul.dll@0xb4f333 	
18 	xul.dll 	nsPIDOMWindow::EnsureInnerWindow 	obj-firefox/dist/include/nsPIDOMWindow.h:342
19 	xul.dll 	nsWindowSH::PreCreate 	dom/base/nsDOMClassInfo.cpp:5077
20 	xul.dll 	ConstructProxyObject 	js/src/xpconnect/src/xpcwrappednative.cpp:3940
21 	xul.dll 	XPCConvert::NativeInterface2JSObject 	js/src/xpconnect/src/xpcconvert.cpp:1190
22 	xul.dll 	XPCConvert::NativeData2JS 	js/src/xpconnect/src/xpcconvert.cpp:487
23 	xul.dll 	XPCConvert::NativeData2JS 	js/src/xpconnect/src/xpcprivate.h:3218
24 	xul.dll 	XPC_WN_CallMethod 	js/src/xpconnect/src/xpcwrappednativejsops.cpp:1610
25 	mozjs.dll 	js::Interpret 	js/src/jsinterp.cpp:4727
26 	mozjs.dll 	js::Invoke 	js/src/jsinterp.cpp:716
27 	mozjs.dll 	js::ExternalInvoke 	js/src/jsinterp.cpp:839
28 	mozjs.dll 	js::Shape::get 	js/src/jsscopeinlines.h:245
29 	mozjs.dll 	js::Interpret 	js/src/jsinterp.cpp:4147
30 	mozjs.dll 	js::Invoke 	js/src/jsinterp.cpp:716
31 	mozjs.dll 	js::ExternalInvoke 	js/src/jsinterp.cpp:839
32 	mozjs.dll 	js::Shape::get 	js/src/jsscopeinlines.h:245
33 	mozjs.dll 	js::Interpret 	js/src/jsinterp.cpp:4147
34 	mozjs.dll 	js::Invoke 	js/src/jsinterp.cpp:716
35 	mozjs.dll 	JS_CallFunctionValue 	js/src/jsapi.cpp:5153
36 	xul.dll 	nsXBLProtoImplAnonymousMethod::Execute 	content/xbl/src/nsXBLProtoImplMethod.cpp:337
37 	xul.dll 	nsXBLBinding::ExecuteAttachedHandler 	content/xbl/src/nsXBLBinding.cpp:980
38 	xul.dll 	nsDocument::MaybeEndOutermostXBLUpdate 	
39 	xul.dll 	nsXULDocument::EndUpdate 	content/xul/document/src/nsXULDocument.cpp:3329
40 	xul.dll 	nsINode::ReplaceOrInsertBefore 	content/base/src/nsGenericElement.cpp:4283
41 	xul.dll 	nsIDOMNode_AppendChild 	obj-firefox/js/src/xpconnect/src/dom_quickstubs.cpp:5783
42 	mozjs.dll 	js::Interpret 	js/src/jsinterp.cpp:4727

Comment 2

[Wayne Mery (:wsmwk)]

next time you have this many tabs open, have a look at how many GDI objects are reported in windows' taskmgr for firefox.exe

Comment 3

[kten50]

(In reply to comment #2)
> next time you have this many tabs open, have a look at how many GDI objects
> are reported in windows' taskmgr for firefox.exe

Thank you for pointing out the "GDI Objects" column. I didn't know that column was important. I have turned on GDI objects in Windows Task Manager so that I can use it next time.

Comment 4

[George Carstoiu]

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:7.0a1) Gecko/20110621 Firefox/7.0a1

Did you try reproducing this issue with a more humane number of opened tabs - I know that Firefox should work exactly the same with either 3 opened tabs or 1000, but we still have to be a bit realistic.

Comment 5

[kten50]

(In reply to comment #4)
> Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:7.0a1) Gecko/20110621
> Firefox/7.0a1
> 
> Did you try reproducing this issue with a more humane number of opened tabs
> - I know that Firefox should work exactly the same with either 3 opened tabs
> or 1000, but we still have to be a bit realistic.

Actually since Firebug upgraded from 1.8a2 to 1.8a3, the problem hasn't cropped up. I have tried and crashes haven't happened. That's why (as I mentioned in comment 0) I initially reported it to the Firebug development team and they advised me to also report it to Firefox, which I did along with the stack traces. I figured there was no harm in filing this bug as you probably get tons of crashes with alpha and beta software and all I was doing was pointing out some specific crashes that I was having. I'm more into PHP and Java/C# programming and don't have experience with C++, so having someone else look at the stack traces didn't seem like a bad idea. 

Right now I have a window open with 41 tabs, another window open with 52 tabs, and a third window open with 247 tabs. Like I have said previously, I know that I'm an edge case.

Also, with the change from builds minefield/alpha/beta/release to channels Nightly/Aurora/Beta/release, I'm starting to think I'm more of an Aurora user under the new system. I may just move over to an Aurora in a week. I never used alphas under the old system because I thought they were too unstable, but Aurora seems to be different than alpha.

Now as for this whole "humane" thing. My view on memory usage is that laptops, netbooks, tablets, and smart phones are for keeping memory as low as possible and the only reason to have a desktop is to let programs spread out to their maximum. I love the work that Firefox developers have done since Firefox 3 on memory consumption and usage. I could only run Firefox 3 up to roughly 600 MB while Firefox 4 could run up to 1.8 GB.

Comment 6

[George Carstoiu]

Mozilla/5.0 (X11; Linux i686; rv:7.0a1) Gecko/20110627 Firefox/7.0a1

Thanks for the interest you present for Firefox. Well, you are right in saying that the Aurora builds are more stable than the Nighlies (alphas), but in the end the last ones are the developers play ground - the place where they introduce new features. Now you'll decide where you think it's the best place to position yourself.

If you consider that the issue you have logged is no longer reproducible, please change the status accordingly and reopen if you encounter it again.

Thanks!

Comment 7

[Wayne Mery (:wsmwk)]

per reporter, caused by add-on