Closed
Bug 112117
Opened 23 years ago
Closed 18 years ago
crash while opening very large number of new browser windows [@ js_AllocGCThing]
Categories
(Core :: XBL, defect)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: aha, Assigned: hyatt)
References
Details
(Keywords: crash)
Crash Data
Attachments
(3 files)
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.6+) Gecko/2001112603. Repro: 1. start mozilla 2. open a new window (with homepage) using Ctrl+N 3. repeat line 2 until mozilla crash Actual: crash (TB38553309W, TB388553148Y) Expected: staying alive
|
||
Comment 2•23 years ago
|
||
Build ID: 2001 11 26 03. Windows 2000. Several GB of disk free. I pressed Ctrl+N more than hundred times with no crash, usually enough for my everyday work. Reporter: Are you low on swap space on disk? If so, Mozilla's handling of low memory may be flawed?
|
Reporter | |
Comment 3•23 years ago
|
||
I think, that memory is enough, physical 392MB, swapfile 430MB. Mozilla crashed with 300 MBs in memory.
|
|
Reporter | |
Comment 4•23 years ago
|
||
Two more talkbacks - TB38554069Q, TB385539556M
Just guessing, could this have to do with (recently fixed) bug 109671 ?
|
||
Comment 6•23 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.6) Gecko/20011120 I can confirm that. 768MB RAM, 90GB disc space
|
||
Comment 7•23 years ago
|
||
CC: stephend@netscape.com, for talkback retrieval, please (TB385539556M)
|
||
Comment 8•23 years ago
|
||
0x31e4e402 js_GetSlotThreadSafe [d:\builds\seamonkey\mozilla\js\src\jslock.c, line 561] JS_GetPrivate [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 1903] js_CloneFunctionObject [d:\builds\seamonkey\mozilla\js\src\jsfun.c, line 1943] JS_CloneFunctionObject [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 2771] DefinePropertyIfFound [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 430] XPC_WN_NoHelper_Resolve [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 706] js_LookupProperty [d:\builds\seamonkey\mozilla\js\src\jsobj.c, line 2216] js_SetProperty [d:\builds\seamonkey\mozilla\js\src\jsobj.c, line 2486] js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2637] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 850] js_InternalInvoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 925] JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3407] nsJSContext::CallEventHandler [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 991] nsJSEventListener::HandleEvent [d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 182] nsXBLPrototypeHandler::ExecuteHandler [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeHandler.cpp, line 443] nsXBLPrototypeHandler::BindingAttached [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeHandler.cpp, line 531] nsXBLPrototypeBinding::BindingAttached [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeBinding.cpp, line 432] nsXBLBinding::ExecuteAttachedHandler [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLBinding.cpp, line 1042] nsBindingManager::ProcessAttachedQueue [d:\builds\seamonkey\mozilla\content\xbl\src\nsBindingManager.cpp, line 917] nsCSSFrameConstructor::ContentInserted [d:\builds\seamonkey\mozilla\layout\html\style\src\nsCSSFrameConstructor.cpp, line 8692] nsCSSFrameConstructor::ContentAppended [d:\builds\seamonkey\mozilla\layout\html\style\src\nsCSSFrameConstructor.cpp, line 7946] StyleSetImpl::ContentAppended [d:\builds\seamonkey\mozilla\content\base\src\nsStyleSet.cpp, line 1412] PresShell::ContentAppended [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5155] nsXULDocument::ContentAppended [d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 2118] nsXULElement::AppendChildTo [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 2373] nsXULElement::InsertBefore [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 1093] nsDocument::AppendChild [d:\builds\seamonkey\mozilla\content\base\src\nsDocument.cpp, line 2924] XPTC_InvokeByIndex [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp, line 154] XPCWrappedNative::CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 2011] XPC_WN_CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 1267] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 834] js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2792] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 850] js_InternalInvoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 925] JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3407] nsJSContext::CallEventHandler [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 991] nsJSEventListener::HandleEvent [d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 182] nsXBLPrototypeHandler::ExecuteHandler [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeHandler.cpp, line 443] nsXBLPrototypeHandler::BindingAttached [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeHandler.cpp, line 531] nsXBLPrototypeBinding::BindingAttached [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeBinding.cpp, line 432] nsXBLBinding::ExecuteAttachedHandler [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLBinding.cpp, line 1042] nsXBLBinding::ExecuteAttachedHandler [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLBinding.cpp, line 1039] nsBindingManager::ProcessAttachedQueue [d:\builds\seamonkey\mozilla\content\xbl\src\nsBindingManager.cpp, line 917] nsCSSFrameConstructor::ContentInserted [d:\builds\seamonkey\mozilla\layout\html\style\src\nsCSSFrameConstructor.cpp, line 8507] StyleSetImpl::ContentInserted [d:\builds\seamonkey\mozilla\content\base\src\nsStyleSet.cpp, line 1421] PresShell::InitialReflow [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2672] nsXULDocument::StartLayout [d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 4388] nsXULDocument::ResumeWalk [d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 5922] nsXULDocument::CachedChromeStreamListener::OnStopRequest [d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 7122] nsDocumentOpenInfo::OnStopRequest [d:\builds\seamonkey\mozilla\uriloader\base\nsURILoader.cpp, line 253] nsCachedChromeChannel::HandleStopLoadEvent [d:\builds\seamonkey\mozilla\rdf\chrome\src\nsChromeProtocolHandler.cpp, line 455] PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591] PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 524] _md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 1072]
Assignee: asa → rogerl
Status: UNCONFIRMED → NEW
Component: Browser-General → Javascript Engine
Ever confirmed: true
QA Contact: doronr → pschwartau
|
||
Comment 9•23 years ago
|
||
Looking up more Talkback incidents from above. I only found one stack trace, from incident TB38554069Q in Comment #4: js_MarkGCThing [d:\builds\seamonkey\mozilla\js\src\jsgc.c, line 795] gc_root_marker [d:\builds\seamonkey\mozilla\js\src\jsgc.c, line 939] JS_DHashTableEnumerate [d:\builds\seamonkey\mozilla\js\src\jsdhash.c, line 601] js_GC [d:\builds\seamonkey\mozilla\js\src\jsgc.c, line 1132] js_AllocGCThing [d:\builds\seamonkey\mozilla\js\src\jsgc.c, line 514] js_NewObject [d:\builds\seamonkey\mozilla\js\src\jsobj.c, line 1610] nsContainerFrame::PositionChildViews [d:\builds\seamonkey\mozilla\layout\html\base\src\nsContainerFrame.cpp, line 782] 0x1c1d0e50
|
|
||
Comment 10•23 years ago
|
||
I cannot duplicate this using debug Mozilla builds 2001-11-26 WinNT, Linux. Adam: Do you return to the first window each time before you hit Ctrl+N? Or do you just keep hitting Ctrl+N? How many Ctrl+N before you crash?
|
|
||
Comment 11•23 years ago
|
||
cc'ing dbaron, jrgm from bug 109671. Does this bug report sound like anything you've seen before? Do the stack traces here indicate anything? I can't reproduce the crash.
|
||
Comment 12•23 years ago
|
||
This doesn't really have anything to do with bug 106971. If someone wants to figure out which set of conditions is causing js to barf, then way to go. But I think we get more bang for the buck focussing on conditions that real users will encounter.
|
|
Reporter | |
Comment 13•23 years ago
|
||
Phil Schwartau: I start browser and just keep pressing Ctrl+N, with actual crash I have to do this about 125 times (first was with about 30 windows). I have setted loading homepage (http://www.alenka.cz/) for new browser. John Morrison: I agree, that conditions are out of normal Mozilla use. But this is the most simply test for testing possibilities of Mozilla (and some newswritter will use it). Futhermore, this crashing could be result of some error in Mozilla's low-architecture. crash with 2001112703/WinNT4 - TB38601734X
|
|
||
Comment 14•23 years ago
|
||
This was all Talkback had for incident TB38601734X: Stack Trace js_AllocGCThing [d:\builds\seamonkey\mozilla\js\src\jsgc.c, line 473] js_NewObject [d:\builds\seamonkey\mozilla\js\src\jsobj.c, line 1610]
|
||
Comment 15•23 years ago
|
||
Last talkback (comment 14) looks like memory corruption; actually, the rest do too. If this is not reproducible, it's going to languish and eventually be marked worksforme. /be
Assignee: rogerl → khanson
|
|
Reporter | |
Comment 16•23 years ago
|
||
crash 2002011503/WinNT4 -> TB1714609K crash 2002011503/Win98 under VMWare -> TB1715770H
|
|
Reporter | |
Comment 18•22 years ago
|
||
I tryed this on different computers with 2002032916. First computer (same as previous crash reports): TB4632122E/Win2K Second computer: TB4632519X/Win98 SR2 (crash in GKLAYOUT.DLL) Third: TB4632550H, TB46326654/Win98 SR2 (crash in JS3250.DLL)
OS: Windows NT → All
|
|
||
Comment 19•22 years ago
|
||
|
|
||
Comment 20•22 years ago
|
||
Adam: thank you for your efforts on this! The latest stack traces do not show a common pattern. The 3rd and 4th are the same as the one in Comment #14, which Brendan identified as memory corruption. Perhaps that's why there's no common pattern for these...
|
|
||
Comment 21•22 years ago
|
||
Is it possible to purify the testcase? Or does that kill purify or run the OS out of memory or some such? /be
|
||
Comment 22•22 years ago
|
||
*** Bug 136767 has been marked as a duplicate of this bug. ***
|
||
Comment 23•22 years ago
|
||
From my dupe - Talkback IDs are TB5060195M and TB5059960M. I also posted a
DrWatson log as attachment 78652 [details] (Let's hope it autolinks.)|
|
||
Comment 24•22 years ago
|
||
|
|
Reporter | |
Comment 25•22 years ago
|
||
2002041711/RC1/Win2K -> TB5373955K, TB5374291H (both before next tests). I hope that memory summary while reproducing could help. If not, sorry for spam =) HW/SW: 2002041711/RC1/Win2K AMDDuron950Mhz/512MB - RAM/693MB - swap Before browser start: Used RAM: 141MB Usable RAM: 385MB On browser load: Used RAM: 152MB Usable RAM: 369MB Mozilla use: 16MB/16MB in virtual memory Browser practically hangs, stop creating new windows: Used RAM: 436MB Usable RAM: 85MB Mozilla use: 300MB/293MB in virtual memory Note: browser eats small memory blocks 4-8kB and 98% CPU is used ... and didn't crash in this case. Another try: Before browser start: Used RAM: 141MB Usable RAM: 383MB On browser load: Used RAM: 152MB Usable RAM: 368MB Mozilla use: 16MB/16MB in virtual memory At crash: Used RAM: 380MB Usable RAM: 131MB -> TB5374357G Another try: Before browser start: Used RAM: 106MB Usable RAM: 396MB On browser load: Used RAM: 117MB Usable RAM: 381MB Mozilla use: 16MB/16MB in virtual memory At crash: Used RAM: 432MB Usable RAM: 56MB Mozilla use: 302MB/300MB in virtual memory -> TB5374565Z
|
||
Comment 26•22 years ago
|
||
is 134419 a duplicat of this? It happens on different ways opening a new mozilla window.
|
|
||
Comment 27•22 years ago
|
||
Excuse I mean bug 143419 (Damn keyboard :-)
|
|
||
Comment 28•22 years ago
|
||
The report in bug 143419 does look similar: > While working on dmoz.org I often click on a link > > <a href="URL" target="_blank">new</a> > > which is inside a <form>. After a while it will crash.
|
|
||
Comment 29•22 years ago
|
||
In the meantime, reassigning this one to Browser-General and cc'ing self. There is no indication that this is due to a bug in JavaScript Engine.
Assignee: khanson → Matti
Component: JavaScript Engine → Browser-General
QA Contact: pschwartau → imajes-qa
|
||
Comment 30•22 years ago
|
||
Reporter: Can you reproduce this with a recent build ?
|
|
Reporter | |
Comment 31•22 years ago
|
||
Using 2002072408/trunk/W2K no crash after simple opening new windows, so original report is WFM (tryed twice). But I experienced something other (which is IMHO relevant to Brendan's comment 15 and comment 21) and also one crash: While Mozilla is eating over 330 MBs of memory (and there are still available RAM), it's stops opening new browser window and also partially stop responding - it should hover personal toolbar items, but no action after click on anything. So I close one browser window and look at JS console, where many errors appears: Error: out of memory In this moment any click produce error in JS console as for example: Error: contentAreaClick is not defined Error: goUpdateGlobalEditMenuItems is not defined I try to open huge bookmark group (pretty hard condition for browser in this situation) and browser crash after few seconds -> TB8718424Y.
|
|
||
Comment 32•22 years ago
|
||
Regarding comment 5: This crash is likely much older. It was commented about in bug 65137 comment 2
|
||
Comment 33•22 years ago
|
||
I was able to recreate on the 2002072808 build on Windows XP Home Edition. Talkback ID: TB8766063Q
Summary: crash while opening very big number of new browser windows → crash while opening very large number of new browser windows
|
|
||
Comment 34•22 years ago
|
||
|
|
||
Comment 35•22 years ago
|
||
-> XBL
Assignee: Matti → hyatt
Component: Browser-General → XBL
QA Contact: imajes-qa → ian
|
||
Comment 36•22 years ago
|
||
wfm for up to 38 new browser windows with Ctl+N winXP 1.3a Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212 reporter: what do you have your homepage set to?
|
|
Reporter | |
Comment 37•22 years ago
|
||
TB16702517E using 2003012508/trunk/W2K with blank page, around 50 browser windows with Modern theme.
|
|
||
Comment 38•22 years ago
|
||
Here is the stack trace for Talkback incident TB16702517E: js_AllocGCThing [js/src/jsgc.c, line 529] js_NewObject [js/src/jsobj.c, line 1646] js_CloneFunctionObject [js/src/jsfun.c, line 1957] 0x1128981c js_Execute [js/src/jsinterp.c, line 1022] JS_ExecuteScript [js/src/jsapi.c, line 3279] nsJSContext::ExecuteScript [dom/src/base/nsJSEnvironment.cpp, line 848] nsXULDocument::ExecuteScript[content/xul/document/src/nsXULDocument.cpp, line 5920] nsXULDocument::LoadScript [content/xul/document/src/nsXULDocument.cpp,line 5702] nsXULDocument::ResumeWalk [content/xul/document/src/nsXULDocument.cpp, line 5465] nsXULDocument::CachedChromeStreamListener::OnStopRequest [content/xul/document/src/nsXULDocument.cpp, line 6910] nsDocumentOpenInfo::OnStopRequest [uriloader/base/nsURILoader.cpp, line 256] nsCachedChromeChannel::HandleStopLoadEvent [rdf/chrome/src/nsChromeProtocolHandler.cpp, line 473] PL_HandleEvent [xpcom/threads/plevent.c, line 664] PL_ProcessPendingEvents [xpcom/threads/plevent.c, line 597] nsEventQueueImpl::ProcessPendingEvents [xpcom/threads/nsEventQueue.cpp,line 391] 0x18a16457
|
||
Comment 39•22 years ago
|
||
That talkback incident data indicates that rt->gcFreeList was 0x1 instead of
null or a valid pointer. The code is heavily optimized and the line number in
the stack isn't very helpful. The crash is actually occuring at line 475.
473: thing = rt->gcFreeList;
474: if (thing) {
475: rt->gcFreeList = thing->next;
476: flagp = thing->flagp;
477: METER(rt->gcStats.freelen--);
478: METER(rt->gcStats.recycle++);
|
||
Comment 40•21 years ago
|
||
*** Bug 206894 has been marked as a duplicate of this bug. ***
|
||
Comment 41•20 years ago
|
||
Had to open 177 windows to crash on my XP system. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 See TB8518K
|
||
Updated•20 years ago
|
Keywords: talkbackid
Whiteboard: TB8518K
|
|
||
Comment 42•20 years ago
|
||
Kevin's talkback stack trace: js_AllocGCThing [/mozilla/js/src/jsgc.c, line 535] js_NewObject [/mozilla/js/src/jsobj.c, line 1822] js_CloneFunctionObject [/mozilla/js/src/jsfun.c, line 1956] JS_CloneFunctionObject [/mozilla/js/src/jsapi.c, line 2922] nsXBLProtoImplProperty::InstallMember [/mozilla/content/xbl/src/nsXBLProtoImplProperty.cpp, line 166] nsXBLProtoImpl::InstallImplementation [/mozilla/content/xbl/src/nsXBLProtoImpl.cpp, line 81] nsXBLPrototypeBinding::InstallImplementation [/mozilla/content/xbl/src/nsXBLPrototypeBinding.cpp, line 428] nsXBLBinding::InstallImplementation [/mozilla/content/xbl/src/nsXBLBinding.cpp, line 816] nsXBLService::LoadBindings [/mozilla/content/xbl/src/nsXBLService.cpp, line 636] nsCSSFrameConstructor::ConstructFrameInternal [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 7013] nsCSSFrameConstructor::ConstructFrame [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 6970] nsCSSFrameConstructor::ProcessChildren [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 11395] nsCSSFrameConstructor::ConstructXULFrame [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 5625] nsCSSFrameConstructor::ConstructFrameInternal [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 7085] nsCSSFrameConstructor::ConstructFrame [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 6970] nsCSSFrameConstructor::ProcessChildren [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 11395] nsCSSFrameConstructor::ConstructXULFrame [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 5625] nsCSSFrameConstructor::ConstructFrameInternal [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 7085] nsCSSFrameConstructor::ConstructFrame [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 6970] nsCSSFrameConstructor::ProcessChildren [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 11395] nsCSSFrameConstructor::ConstructXULFrame [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 5625] nsCSSFrameConstructor::ConstructFrameInternal [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 7085] nsCSSFrameConstructor::ConstructFrame [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 6970] nsCSSFrameConstructor::ProcessChildren [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 11395] nsCSSFrameConstructor::ConstructDocElementFrame [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 3473] nsCSSFrameConstructor::ContentInserted [/mozilla/layout/html/style/src/nsCSSFrameConstructor.cpp, line 8666] PresShell::InitialReflow [/mozilla/layout/html/base/src/nsPresShell.cpp, line 2776] nsXULDocument::StartLayout [/mozilla/content/xul/document/src/nsXULDocument.cpp, line 2188] nsXULDocument::ResumeWalk [/mozilla/content/xul/document/src/nsXULDocument.cpp, line 3041] nsXULDocument::CachedChromeStreamListener::OnStopRequest [/mozilla/content/xul/document/src/nsXULDocument.cpp, line 4193] nsDocumentOpenInfo::OnStopRequest [/mozilla/uriloader/base/nsURILoader.cpp, line 361] nsCachedChromeChannel::HandleStopLoadEvent [/mozilla/rdf/chrome/src/nsChromeProtocolHandler.cpp, line 477] PL_HandleEvent [/mozilla/xpcom/threads/plevent.c, line 672] PL_ProcessPendingEvents [/mozilla/xpcom/threads/plevent.c, line 610] _md_EventReceiverProc [/mozilla/xpcom/threads/plevent.c, line 1413] USER32.dll + 0x3d79 (0x77d43d79) USER32.dll + 0x3ddf (0x77d43ddf) nsAppShellService::Run [/mozilla/xpfe/appshell/src/nsAppShellService.cpp, line 524] main1 [/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1308] main [/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1712] WinMain [/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1734] WinMainCRTStartup() kernel32.dll + 0x214c7 (0x77e814c7)
Keywords: talkbackid
Whiteboard: TB8518K
|
|
Reporter | |
Updated•20 years ago
|
Summary: crash while opening very large number of new browser windows → crash while opening very large number of new browser windows [@ js_AllocGCThing]
|
||
Comment 43•20 years ago
|
||
I think I became a victim of this one after opening around 6 tabs at the 7-zip forums on SourceForge. Yeah, around six, certainly not a dozen or even more. I think it's this bug I got since it was definitely related to opening tabs. I think it crashed while still loading them. The talkback id is TV1454137Z and here's a link to it: http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TV1454137Z I am using a Firefox 1.0 aviary branch build: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041011 Firefox/0.10
|
||
Comment 44•20 years ago
|
||
I'm not sure if my bug is the same one or not, but I figured I'd throw it out there here before I actually start a new one. TB2556594W has whatever you get out of those traces. What makes mine somewhat different from what's described above is, mine (Firefox 1.0 release) crashes when I open up just two or three windows right after startup, and the Home Page location is set to "about:blank" so it's not exactly being overtaxed there. My system has 768MB physical RAM, and about 3GB of swap, so that shouldn't be an issue either, especially for only 2-3 new pages. It happens whether I open them with Ctl-N or Menu->File->New Window. I think it's new; I think I would have noticed it if it had been the same for 0.9.3. I'm running on Fedora Core 2, Linux kernel 2.6.9, and in case interaction with the X server/desktop environment/window manager might be involved, I'm using XOrg 6.7.0, Gnome 2.6.0 or 2.6.2 (depending which package I look at), and Sawfish 1.3 as my window manager. Not a lot of Sawfish users out there, I suspect, so perhaps that might be why there aren't many, many reports of such behaviour. Of course, I wouldn't feel such a need to open 2-3 new windows right away if new windows didn't seem to open slower after a period of browsing & creating new tabs.... grumble, grumble. ;) I might be checking that one for existing bugs and/or opening a new one, too.
|
||
Comment 45•18 years ago
|
||
WFM, no probs. any reason why this bug should not be closed? FF - ~370 windows of about:blank and 30 mozillazine.org Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060830 Minefield/3.0a1 (2 minutes to shut down) SM - 402 windows of www.google.com, plus 30 http://www.alenka.cz/ from comment 13 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2 (but didn't shut down nicely - probably windows thrashing and/or bugs in gecko garbage collection)
|
|
Reporter | |
Comment 46•18 years ago
|
||
-> Let's mark it as WFM and reopen if repro re-appear.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
|
||
Updated•13 years ago
|
Crash Signature: [@ js_AllocGCThing]
You need to log in
before you can comment on or make changes to this bug.
Description
•