Closed Bug 545870 Opened 14 years ago Closed 1 month ago

[OOPP] mozilla-runtime stays alive after firefox crashes

Categories

(Core :: IPC, defect)

x86
Windows 7
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: benjamin, Unassigned)

References

Details

(Whiteboard: [bugday0601])

mozilla-runtime sometimes stays alive after Firefox crashes on Windows. I have a copy here and the stacks are kinda bogus:

I/O thread:
>	ntdll.dll!_NtRemoveIoCompletion@20()  + 0x15 bytes	
 	ntdll.dll!_NtRemoveIoCompletion@20()  + 0x15 bytes	
 	msvcr90d.dll!operator delete(void * pUserData=0x006f1da8)  Line 57 + 0x7 bytes	C++
 	xul.dll!6d8b2214() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for xul.dll]	

plugin thread:
>	ntdll.dll!_NtWaitForMultipleObjects@20()  + 0x15 bytes	
 	ntdll.dll!_NtWaitForMultipleObjects@20()  + 0x15 bytes	
 	xul.dll!6d817ba0() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for xul.dll]	

I think that the I/O thread is *probably* at:
http://mxr.mozilla.org/mozilla-central/source/ipc/chromium/src/base/message_pump_win.cc#509
leading to
http://mxr.mozilla.org/mozilla-central/source/ipc/chromium/src/chrome/common/ipc_channel_win.cc#57

Haven't tried to reproduce this yet...
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100601 BRI/1 Minefield/3.7a5pre

I'm unable to reproduce this behaviour.  I loaded the Bing toolbar and had a youtube video playing in a tab.  I also opened task manager to view the processes.  I tried to trigger a crash several ways:

1. End Process Firefox.exe from task manager
2. All methods available using the CrashMe! Advanced extension

All of these successfully closed firefox.exe and all running plugin-container.exe

Benjamin, can you please assist in identifying steps to reproduce?  Otherwise this may be WONTFIX/INVALID/INCOMPLETE/WORKSFORME.
Whiteboard: [bugday0601]
This was a very specific problem caught in recording (and since lost). I think it should stay open for a while.
Severity: normal → S3

(In reply to Benjamin Smedberg from comment #2)

This was a very specific problem caught in recording (and since lost). I
think it should stay open for a while.

14 year is probably long enough.

Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.