Closed Bug 69662 Opened 24 years ago Closed 24 years ago

Eventhandler crashing in various situations

Categories

(Core :: XPCOM, defect)

x86
BeOS
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 87337
Future

People

(Reporter: rosenauer, Assigned: rpotts)

References

Details

(Keywords: crash)

I hope I have found the right component;) Using the latest build, 2001021912 under BeOS, I get crashes when an URL is retrieved, but the connection is about to time out / has timed out. Mostly I get one or two "Connection timed out"-messages, but then - in 50% of the cases or so - Mozilla crashes. I have some stackcrawls for you: * crash when closing the Prefs (was changing Proxy-settings and pressing OK, after the window closed, I got the crash) loading symbols segment violation occurred _pl_GetEventCount: _pl_GetEventCount: +0031 ec875311: * 128b movl (%edx), %edx mozilla-bin:sc frame retaddr fd001854 ec87537a PL_ProcessPendingEvents + 0000004e fd00186c ecace7b9 nsAppShell::Run(void) + 00000105 fd001898 eca548a8 nsAppShellService::Run(void) + 00000024 fd0018a8 8000968b main1(int, char **, nsISupports *) + 00000943 fd0019f8 80009c9b main + 0000011b fd001a24 80006a05 _start + 00000061 mozilla-bin:regs eax 8138a9ac ebp fd001854 cs 001b edx 00000005 esi 8138a9a8 ss 0023 ecx 8138e9b5 edi 00000005 ds 0023 ebx ec8c40cc esp fd001848 es 0023 fs 297b eflags 00010207 eip ec875311 trap_no 0000000e error_code 00000004 mozilla-bin:ps PID DEBUG NAME STATUS 520 curr mozilla-bin semaphore 523 BApplication semaphore 528 moz-thread ready 52c timer roster semaphore 537 w>Advantages and/of disadvantag semaphore 544 w>Mozilla {Build ID: 2001021912 semaphore 55d select-thread semaphore 55e select-thread semaphore 560 select-thread semaphore 562 w> semaphore 567 w> semaphore 56e w>Compose: Re: Advantages and/o semaphore 574 w>Alert semaphore 578 w>Alert semaphore 59a w> semaphore 59b w> semaphore 59d w> semaphore 59e w> semaphore 5a1 w>Alert semaphore 5a2 moz-thread semaphore 5a3 w>Preferences semaphore 5a4 team 181 debugtask semaphore mozilla-bin: * crash after timeout: loading symbols segment violation occurred atomic_add1: atomic_add1: +0008 ec083cbd: * f0 lock mozilla-bin:sc frame retaddr fd001850 ed02ebb6 #File libnspr4.so text + 00020bb6 fd001864 ecfbc352 PL_ProcessPendingEvents + 00000026 fd00187c edfb57b9 nsAppShell::Run(void) + 00000105 fd0018a8 eda7c8a8 nsAppShellService::Run(void) + 00000024 fd0018b8 8000968b main1(int, char **, nsISupports *) + 00000943 fd001a08 80009c9b main + 0000011b fd001a34 80006a05 _start + 00000061 mozilla-bin:regs eax 00000000 ebp fd001850 cs 001b edx 80000003 esi 80000003 ss 0023 ecx 00000001 edi 80000007 ds 0023 ebx 80000007 esp fd001834 es 0023 fs 51b3 eflags 00010202 eip ec083cbd trap_no 0000000e error_code 00000007 mozilla-bin:ps PID DEBUG NAME STATUS a27 curr mozilla-bin semaphore a2a timer roster semaphore a2b BApplication semaphore a30 moz-thread snoozing a82 w>Advantages and/of disadvantag semaphore a8a w> semaphore a8c w> semaphore a8f w> semaphore aa5 select-thread semaphore aa6 select-thread semaphore ab7 w> semaphore aba w>THE BEOS OPERATING SYSTEM: AN semaphore ac0 moz-thread semaphore ac1 w> semaphore ac2 w> semaphore ac4 w>Preferences semaphore ac9 w> semaphore ada w>Mozilla {Build ID: 2001021912 semaphore adc w> semaphore ade w>Alert semaphore adf team 362 debugtask semaphore mozilla-bin: #2: loading symbols segment violation occurred ec7f0ba3: * 084239 cmpl %eax, 0x00000008(%edx) mozilla-bin:sc frame retaddr fd001854 ec6fd352 PL_ProcessPendingEvents + 00000026 fd00186c eca1e7b9 nsAppShell::Run(void) + 00000105 fd001898 ec9838a8 nsAppShellService::Run(void) + 00000024 fd0018a8 8000968b main1(int, char **, nsISupports *) + 00000943 fd0019f8 80009c9b main + 0000011b fd001a24 80006a05 _start + 00000061 mozilla-bin:regs eax 00000271 ebp fd001854 cs 001b edx 00000038 esi 81627918 ss 0023 ecx 00000000 edi 809c8680 ds 0023 ebx ec7f4b20 esp fd00184c es 0023 fs 1403 eflags 00010292 eip ec7f0ba3 trap_no 0000000e error_code 00000004 mozilla-bin:ps PID DEBUG NAME STATUS 271 curr mozilla-bin semaphore 274 BApplication semaphore 279 moz-thread ready 27d timer roster semaphore 28b w>Advantages and/of disadvantag semaphore 291 w> semaphore 293 w>Account Settings semaphore 2c9 select-thread semaphore 2ca select-thread ready 2cb select-thread semaphore 2dd w>Alert semaphore 2e5 w>Alert semaphore 307 w>Account Settings semaphore 313 select-thread semaphore 31f w>Mozilla {Build ID: 2001021901 semaphore 32a w>Alert semaphore 336 moz-thread semaphore 339 w>Compose: Re: CVSROOT semaphore 344 w>Alert semaphore 346 w> semaphore 34b w>Compose: Re: CVSROOT semaphore 359 w> semaphore 35d w>Alert semaphore 361 w>Message Compose semaphore 364 w> semaphore 366 w>Alert semaphore 367 team 142 debugtask semaphore mozilla-bin:
arg, forgot another one, this one seems to be more interesting: loading symbols segment violation occurred 811ee278: * c0ecbe5cc0 rcrb $0xc0, -0x00000014(%esi,%edi,4) mozilla-bin:sc frame retaddr fd001464 ece2c96f nsURILoader::ShouldHandleContent(nsIURIContentListener *, char const *, int, char const *, char **) + 00000047 fd001494 ece2ca70 nsURILoader::DispatchContent(char const *, int, char const *, nsIChannel *, nsISupports *, nsIURIContentListener *, nsISupports *, char **, nsIURIContentListener **, int *) + 000000d4 fd00152c ece2a20a nsDocumentOpenInfo::DispatchContent(nsIChannel *, nsISupports *) + 0000023e fd00166c ece29eb1 nsDocumentOpenInfo::OnStartRequest(nsIChannel *, nsISupports *) + 000000c9 fd0016a4 ecd17130 nsHTTPFinalListener::OnStartRequest(nsIChannel *, nsISupports *) + 0000004c fd0016bc ecd361f6 InterceptStreamListener::OnStartRequest(nsIChannel *, nsISupports *) + 0000002e fd0016dc ecd16e58 nsHTTPServerListener::FinishedResponseHeaders(void) + 00000044 fd0016fc ecd1590e nsHTTPServerListener::OnDataAvailable(nsIChannel *, nsISupports *, nsIInputStream *, unsigned int, unsigned int) + 00000416 fd001808 eccd6f20 nsOnDataAvailableEvent::HandleEvent(void) + 000000b4 fd00183c eccd66ce nsStreamObserverEvent::HandlePLEvent(PLEvent *) + 00000026 fd00184c ec875487 PL_HandleEvent + 0000001f fd001864 ec8753a3 PL_ProcessPendingEvents + 00000077 fd00187c ecace7b9 nsAppShell::Run(void) + 00000105 fd0018a8 eca548a8 nsAppShellService::Run(void) + 00000024 fd0018b8 8000968b main1(int, char **, nsISupports *) + 00000943 fd001a08 80009c9b main + 0000011b fd001a34 80006a05 _start + 00000061 mozilla-bin:regs eax 811ee278 ebp fd001464 cs 001b edx 81528618 esi fd001490 ss 0023 ecx 8163ebe8 edi fd00163c ds 0023 ebx ece1961c esp fd00143c es 0023 fs 2f83 eflags 00010286 eip 811ee278 trap_no 0000000e error_code 00000006 mozilla-bin:ps PID DEBUG NAME STATUS 5e1 curr mozilla-bin semaphore 5e4 BApplication semaphore 5e9 moz-thread ready 5ed timer roster semaphore 5f5 w>BeOS Headlines by yaBel.com - semaphore 5fe w> semaphore 600 w> semaphore 602 select-thread semaphore 603 select-thread ready 607 w> semaphore 60d w>Preferences semaphore 60f w> semaphore 619 w>Advantages and/of disadvantag semaphore 624 w>Alert semaphore 626 w>Alert semaphore 631 w> semaphore 635 moz-thread semaphore 636 w>Compose: Re: Advantages and/o semaphore 639 w>Alert semaphore 63c w> semaphore 63d w> semaphore 63f w> semaphore 641 w>Mozilla {Build ID: 2001021912 semaphore 64c team 205 debugtask semaphore mozilla-bin:
PLEvent has been moved to XPCOM. If we assign bugs by where the program crashes, this bug should be assigned to Browser:XPCOM.
Assignee: wtc → rpotts
Component: NSPR → Threading
Product: NSPR → Browser
QA Contact: wtc → rpotts
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → Future
gagan, how do we do w/ timedout connections?
Severity: major → critical
Keywords: crash
Potential patch in bug 87337. Marking dependent.
Depends on: 87337
*** This bug has been marked as a duplicate of 87337 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
sure
Status: RESOLVED → VERIFIED
Moving all threading bugs to XPCOM. See bug 160356.
Component: Threading → XPCOM
You need to log in before you can comment on or make changes to this bug.