138205 - N701 M121 Trunk crashing after sending multiple dialogs [@ GlobalWindowImpl::DropTimeout]

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect)

Description

[greer]

This crash has started appearing in the early M1.0 branch data. There is not a
large volume of data for the branch yet, but the Trunk is also showing this
signature and this may prove to be a larger problem when the releases have a
wider audience.

  It appears that users are getting multiple alert dialogs when requesting a
search that finds no matches. Closing those dialogs crashes the browser.

M100 (GlobalWindowImpl::DropTimeout):        2
(5324682) - 2002-04-17  [Windows 98  4.90 build 73010104] (Build: 2002041514)

Trunk (GlobalWindowImpl::DropTimeout):       12
(5036798) - [Windows NT  4.0 build 1381] (Build 2002040711):  jdialog in frames
view URL: java 1.4 sdk
(5164638) - [Windows 98  4.90 build 73010104] (Build 2002041210): opening the
page URL: http://server19.hypermart.net/dontbuycdsorg/
(5164386) - [Windows NT  5.0 build 2195] (Build 2002041210): Using the DOM
inspector to find a component by ID.  I think I entered a component that did not
exist.  A pair of alert dialogs appear.  When I closed them  Mozilla keeled over.  
(5310651) - [Linux 2.4.18] (Build 2002041609): attempting to find in file  I
searched three times for something that only appeared twice in the file.  I got
two copies of the ``The text is not found'' dialogs  and then mozilla crashed.

Comment 1

[Jay Patel [:jay]]

Here's a recent incident with a stack and some helpful comments that might help
us reproduce:

 Incident ID 5310651   
Stack Signature  GlobalWindowImpl::DropTimeout() ce5295f3
Trigger Time 2002-04-17 12:24:52
Email Address
URL visited
Build ID 2002041609
Product ID MozillaTrunk
Platform LinuxIntel
Operating System Linux 2.4.18
Module libjsdom.so
Trigger Reason SIGSEGV: Segmentation Fault: (signal 11)
User Comments attempting to find in file, I searched three times for something
that only appeared twice in the file. I got two copies of the ``The text is not
found'' dialogs, and then mozilla crashed.
Stack Trace
GlobalWindowImpl::DropTimeout()
GlobalWindowImpl::TimerCallback()
nsTimerImpl::Fire()
handleTimerEvent()
PL_HandleEvent()
PL_ProcessPendingEvents()
nsEventQueueImpl::ProcessPendingEvents()
event_processor_callback()
our_gdk_io_invoke()
libglib-1.2.so.0 + 0xff9e (0x4038ef9e)
libglib-1.2.so.0 + 0x11773 (0x40390773)
libglib-1.2.so.0 + 0x11d39 (0x40390d39)
libglib-1.2.so.0 + 0x11eec (0x40390eec)
libgtk-1.2.so.0 + 0x94333 (0x402ab333)
nsAppShell::Run()
nsAppShellService::Run()
main1()
main()
libc.so.6 + 0x1c647 (0x404ee647) 

And a Windows incident with line numbers in the stack:
 Incident ID 5164386   
Stack Signature  GlobalWindowImpl::DropTimeout 4c560ab2
Trigger Time 2002-04-13 13:19:30
Email Address
URL visited
Build ID 2002041210
Product ID MozillaTrunk
Platform Win32
Operating System Windows NT 5.0 build 2195
Module jsdom.dll
Trigger Reason Access violation
User Comments Using the DOM inspector to find a component by ID. I think I
entered a component that did not exist. A pair of alert dialogs appear. When I
closed them, Mozilla keeled over.
Stack Trace
GlobalWindowImpl::DropTimeout
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 4549]
GlobalWindowImpl::TimerCallback
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 4751]
nsTimerImpl::Process [d:\builds\seamonkey\mozilla\xpcom\threads\nsTimerImpl.cpp,
line 330]
handleMyEvent [d:\builds\seamonkey\mozilla\xpcom\threads\nsTimerImpl.cpp, line 381]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 597]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 530]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1078]
nsAppShellService::Run
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp, line 309]
main1 [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1430]
main [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1765]
WinMain [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1783]
WinMainCRTStartup()
KERNEL32.DLL + 0x17d08 (0x77e97d08) 

Adding topcrash keyword since this has the potential to be a topcrash from
looking at early M100 data.

Comment 2

[timeless]

see also bug 68488, bug 79920, bug 84933, bug 91996 (?), bug 94443, bug 94659

Comment 3

[Jan Carpenter]

Topcrash on M1RC1
Adding M1RC1 to summary for tracking

Build ID range: 2002041717 to 2002041717

Stack Trace: 

	 GlobalWindowImpl::DropTimeout
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp  line 4542]
	 GlobalWindowImpl::TimerCallback
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp  line 4744]
	 nsTimerImpl::Process
[d:\builds\seamonkey\mozilla\xpcom\threads\nsTimerImpl.cpp  line 330]
	 handleMyEvent
[d:\builds\seamonkey\mozilla\xpcom\threads\nsTimerImpl.cpp  line 381]
	 PL_HandleEvent
[d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c  line 597]
	 PL_ProcessPendingEvents
[d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c  line 530]
	 _md_EventReceiverProc
[d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c  line 1078]
	 KERNEL32.DLL + 0x24407 (0xbff94407)
	 0x00648c16
 
 	Source File :
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/dom/src/base/nsGlobalWindow.cpp
line : 4542

COMMENTS/URLs:
     (5471853)	Comments: listen to realaoudio
     (5454522)	Comments: was trying to subscribe to a netscape newsgroup
     (5410754)	Comments: I was ctrl+F searchong on a (tabbed browser) page and when
finished I hit enter. no more mozilla.mozilla gone dead :(
     (5402700)	URL: www.xulplanet.org
     (5402700)	Comments: changing preferences (tabbed browsing)

Comment 4

[timeless]

.

Comment 5

[Jan Carpenter]

The last build this bug crashed in (according to talkback is 2002062208.  Fixed?

Comment 6

[Jay Patel [:jay]]

There was one crash with a 7/15 MozillaTrunk build...so this crash is still
around.  Probably just not in high numbers on the Trunk.  We'll have to wait for
some Mozilla 1.1 Beta Talkback data to see if this is still a major issue or not.

Comment 7

[Matthias Versen [:Matti]]

*** Bug 177249 has been marked as a duplicate of this bug. ***

Comment 8

[Heikki Toivonen (remove -bugzilla when emailing directly)]

jpatel: Some issues like this were fixed recently, can you check talkback data
if this still appears?

Comment 9

[Jay Patel [:jay]]

Taking a look at the latest Talkback data, it looks like this crash is gone. 
The most recent incidents are with Mozilla 1.1 and Mozilla 1.2.1
(Mozilla1.2Win322002113012).  

This continues to be a problem on the Gecko 1.0 branch (it is a topcrasher for
Netscape 7.01)...but in terms of being a problem with the MozillaTrunk, it is no
longer crashing.  Worksforme?

Comment 10

[Jay Patel [:jay]]

Based on the last 2 comments, I'm marking this worksforme.  It is no longer a
concern on the MozillaTrunk.