Closed Bug 118239 Opened 24 years ago Closed 23 years ago

Mac OS X: Quitting the application during splash screen results in a crash

Categories

(Core :: DOM: HTML Parser, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
mozilla1.2alpha

People

(Reporter: chrispetersen, Assigned: jag+mozilla)

Details

(Keywords: crash)

Build: 2002-01-03-08 Platform: Mac OS X Expected Results: App should simply quit with no crash reported What I got: Crash occurs. Steps to reproduce: 1) Launch App 2) When startup screen appears, press command -Q 3) Application crashes ********** Date/Time: 2002-01-04 14:23:01 -0800 OS Version: 10.1.2 (Build 5P48) Command: Netscape 6 PID: 2767 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0: #0 0x0062c950 in Compare2To1(char const *, char const *, unsigned int, int) #1 0x0062c8e8 in Compare2To1(char const *, char const *, unsigned int, int) #2 0x0062dfc0 in nsStr::FindSubstr(nsStr const &, nsStr const &, int, int, int) #3 0x00634538 in nsString::Find( const(char const *, int, int, int)) #4 0x01d021b8 in CNavDTD::CanParse(CParserContext &, nsString const &, int) #5 0x01d28458 in FindSuitableDTD(CParserContext &, nsString &) #6 0x01d289a8 in nsParser::WillBuildModel(nsString &) #7 0x01d29ba8 in nsParser::ResumeParse(int, int) #8 0x01d2c3c0 in OnDataAvailable__8nsParserFP10nsIRequestP11nsISupportsP14nsIIn #9 0x01bc8ce4 in OnDataAvailable__12nsJARChannelFP10nsIRequestP11nsISupportsP14 #10 0x01bd4120 in nsOnDataAvailableEvent::HandleEvent(void) #11 0x01be2ce0 in nsARequestObserverEvent::HandlePLEvent(PLEvent *) #12 0x005f6c00 in PL_HandleEvent #13 0x005f6a6c in PL_ProcessPendingEvents #14 0x0059d2ac in nsEventQueueImpl::ProcessPendingEvents(void) #15 0x005c8288 in NS_ShutdownXPCOM #16 0x004ccf14 in main Thread 1: #0 0x7000497c in syscall #1 0x70557600 in BSD_waitevent #2 0x70554b80 in CarbonSelectThreadFunc #3 0x7002054c in _pthread_body Thread 2: #0 0x7003f4c8 in semaphore_wait_signal_trap #1 0x7003f2c8 in _pthread_cond_wait #2 0x705593ec in CarbonOperationThreadFunc #3 0x7002054c in _pthread_body Thread 3: #0 0x70044cf8 in semaphore_timedwait_signal_trap #1 0x70044cd8 in semaphore_timedwait_signal #2 0x7003f2b8 in _pthread_cond_wait #3 0x70283ea4 in TSWaitOnConditionTimedRelative #4 0x7027d748 in TSWaitOnSemaphoreCommon #5 0x702c2078 in TimerThread #6 0x7002054c in _pthread_body Thread 4: #0 0x7003f4c8 in semaphore_wait_signal_trap #1 0x7003f2c8 in _pthread_cond_wait #2 0x70250ab0 in TSWaitOnCondition #3 0x7027d730 in TSWaitOnSemaphoreCommon #4 0x70243d14 in AsyncFileThread #5 0x7002054c in _pthread_body PPC Thread State: srr0: 0x0062c950 srr1: 0x0000f030 vrsave: 0x00000000 xer: 0x00000018 lr: 0x0062c8e8 ctr: 0x700056fc mq: 0x00000000 r0: 0x0000003c r1: 0xbffff040 r2: 0x00104000 r3: 0x00000000 r4: 0x00000074 r5: 0xbffff07a r6: 0x000fd1cc r7: 0xbfffef60 r8: 0x0004c2a4 r9: 0x80240e10 r10: 0x00000024 r11: 0x80003710 r12: 0x700056fc r13: 0x00000000 r14: 0x00000036 r15: 0x00531450 r16: 0x00531480 r17: 0xbfffee90 r18: 0x00530918 r19: 0x00002807 r20: 0x00000000 r21: 0x0000001c r22: 0x70004234 r23: 0x700042c8 r24: 0x00000004 r25: 0x000006eb r26: 0x8081ab5c r27: 0x00535330 r28: 0x00000000 r29: 0xbfffef00 r30: 0x00000000 r31: 0x00000001 **********
I will try a Classic build under OS 9.2.2 to see if it occurs.
This problem is not occuring under OS 9.2.2 with the Classic build (2002-01-03-08). Application finishes (loading it's menu and opening browser window ) and then quits gracefully.
Keywords: crash
Summary: Quitting the application during splash screen results in a crash → Mac OS X: Quitting the application during splash screen results in a crash
pink? it's pretty easy for me to repro this...
Assignee: trudelle → pinkerton
Keywords: nsbeta1
crashes in parser or strings. jag? (why did this go to me? just cuz it crashes on a mac?)
Assignee: pinkerton → harishd
Component: XP Apps → Parser
QA Contact: sairuh → moied
Harish, Is this issue any closer to being resolved ?
Chris: I haven't gotten the chance to take a look into this bug [ plus I'm MAC clueless :-( ]. But looking at the stack it looks more like a string bug than a parser bug. I'm going to reassign this bug to Jag for further investigation.
Assignee: harishd → jaggernaut
nsbeta1+ per Nav triage team, worth fixing if we can, but would ship without it.
Keywords: nsbeta1nsbeta1+
-> 1.0
Target Milestone: --- → mozilla1.0
nsbeta1- per ADT
Keywords: nsbeta1+nsbeta1-
Target Milestone: mozilla1.0 → mozilla1.2
Using release 1.2.1, OS X 10.2.2, I am unable to quit during splash screen. The quit command does not fire until after Mozilla has finished loading.
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.
Severity: major → critical
Sorry for the repeat comment, but... this bug WORKSFORME. Anyone else test it recently? I've tried repeatedly to quit during launch, but Mozilla just keeps loading. The first browser window shows, then it quits normally.
well, it does.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.