Closed Bug 238970 Opened 22 years ago Closed 20 years ago

stable for days, then crash (also Firefox); cannot launch both after reboot or cold boot; logs available; other apps affectedt

Categories

(SeaMonkey :: General, defect)

PowerPC
Other
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mogiljan, Unassigned)

Details

(Keywords: crash)

User-Agent: Mozilla/4.5 (compatible; iCab 2.9.7; Macintosh; U; PPC) Build Identifier: 1.6 for OS X Mac OS X Version 10.2.8 (Build 6R73) Mar 28 07:06:46 localhost WindowServer[197]: CGXDisableUpdate: Updates disabled by connection 0x5b0f for over 1.000000 seconds /Mozilla.app/Contents/MacOS/mozilla-bin: can't map file: /Mozilla.app/Contents/MacOS/plugins/Default Plugin.plugin ((os/kern) invalid argument) /Mozilla.app/Contents/MacOS/mozilla-bin: can't map file: /Library/Internet Plug-Ins/DRM Plugin.bundle ((os/kern) invalid argument) /Mozilla.app/Contents/MacOS/mozilla-bin: can't map file: /Library/Internet Plug-Ins/QuickTime Plugin.plugin ((os/kern) invalid argument) /Mozilla.app/Contents/MacOS/mozilla-bin: can't map file: /Library/Internet Plug-Ins/Java Applet.plugin ((os/kern) invalid argument) dyld: /Mozilla.app/Contents/MacOS/mozilla-bin Undefined symbols: JavaVM undefined reference to [getenv expected to be defined in /usr/lib/libSystem.B.dylib Mar 28 07:08:05 localhost crashdump: Crash report written to: /Users/xxxxx/Library/Logs/CrashReporter/mozilla-bin.crash.log Mar 28 07:08:25 localhost WindowServer[197]: CGXMapShmem : Invalid shared memory id Mar 28 07:08:25 localhost WindowServer[197]: CGXGetShmemSize : Invalid shared memory id Mar 28 07:08:25 localhost /iCab.app/Contents/MacOS/iCab: kCGErrorIllegalArgument : CGSMapShmem : Cannot map shared memory Mar 28 07:08:25 localhost WindowServer[197]: CGXMapShmem : Invalid shared memory id Mar 28 07:08:25 localhost WindowServer[197]: CGXGetShmemSize : Invalid shared memory id Mar 28 07:08:25 localhost /iCab.app/Contents/MacOS/iCab: kCGErrorIllegalArgument : CGSMapShmem : Cannot map shared memory Mar 28 07:11:35 localhost crashdump: Crash report written to: /Users/xxxx/Library/Logs/CrashReporter/iCab.crash.log Reproducible: Always Steps to Reproduce: 1. erased Firfox 0.8 and re-installed; does not launch. 2.Mozilla - did not erase yet; worked great all day Sat.; does not launch Sun. 3. Actual Results: cannot launch; see above text in Details section; Crash logs available Expected Results: Most times OS X provides a dialogue box saying "your app has crashed, but the others are unaffected". This is not always happening upon crashing. Very strange that both Firefox and Mozilla do not open(launch).
I would be surprised if the shared memory errors had anything to do with your lizards. May I suggest that you boot into single user mode and run fsck? I have only seen dyld errors when I have had something radically wrong with my system. Ben
Summary: stable for days, then crash (also Firefox); cannot launch both after reboot or cold boot; logs available; other apps affectedt → stable for days, then crash (also Firefox); cannot launch both after reboot or cold boot; logs available; other apps affectedt
(In reply to comment #1) > I would be surprised if the shared memory errors had anything to do > with your lizards. > > May I suggest that you boot into single user mode and run fsck? > > I have only seen dyld errors when I have had something radically > wrong with my system. > > Ben Thanks, Ben. I ran fsck twice but no errors. Re-installed Firefox - works ok. Mozilla will be next? If bug re-occurs, I won't repost. Logs available, here's the Firefox log from before the new install (comments welcome): Date/Time: 2004-03-25 14:42:09 -0500 OS Version: 10.2.8 (Build 6R73) Host: xxxxx-Computer.local. Command: firefox-bin PID: 374 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x67653a60 Thread 0 Crashed: Thread 1: #0 0x9002568c in select #1 0x0151f77c in poll #2 0x0151bfc8 in _pr_poll_with_poll #3 0x000bde98 in _ZN24nsSocketTransportService3RunEv #4 0x0504614c in _ZN8nsThread4MainEPv #5 0x0151d410 in _pt_root #6 0x90020c28 in _pthread_body Thread 2: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x928ec28c in JNI_CreateJavaVM_Impl #3 0x928ec224 in JNI_CreateJavaVM_Impl #4 0x928a51fc in JVM_GetClassMethodsCount #5 0x90020c28 in _pthread_body Thread 3: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x9283de9c in JVM_NewInstance #3 0x9285eae4 in JVM_FillInStackTrace #4 0x928647a0 in JVM_Send #5 0x9290114c in JNI_CreateJavaVM_Impl #6 0x928a51fc in JVM_GetClassMethodsCount #7 0x90020c28 in _pthread_body Thread 4: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x92845d80 in JVM_ArrayCopy #4 0x9285d620 in JVM_MonitorNotify #5 0x9285e2f8 in JVM_MonitorWait #6 0x0a12f668 in 0xa12f668 #7 0x0a12d68c in 0xa12d68c #8 0x0a12d68c in 0xa12d68c #9 0xa2843c38 in _ZTSSt13bad_exception #10 0x92838bdc in JVM_CurrentTimeMillis #11 0x92878c28 in JVM_FindClassFromClass #12 0x92892c90 in JVM_IsSameClassPackage #13 0x9288cf70 in JVM_GetMethodIxExceptionTableEntry #14 0x928787a0 in JVM_FindClassFromClass #15 0x928a51fc in JVM_GetClassMethodsCount #16 0x90020c28 in _pthread_body Thread 5: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x92845d80 in JVM_ArrayCopy #4 0x9285d620 in JVM_MonitorNotify #5 0x9285e2f8 in JVM_MonitorWait #6 0x0a12f668 in 0xa12f668 #7 0x0a12d68c in 0xa12d68c #8 0x0a12d5cc in 0xa12d5cc #9 0x0a12d5cc in 0xa12d5cc #10 0xa2843c38 in _ZTSSt13bad_exception #11 0x92838bdc in JVM_CurrentTimeMillis #12 0x92878c28 in JVM_FindClassFromClass #13 0x92892c90 in JVM_IsSameClassPackage #14 0x9288cf70 in JVM_GetMethodIxExceptionTableEntry #15 0x928787a0 in JVM_FindClassFromClass #16 0x928a51fc in JVM_GetClassMethodsCount #17 0x90020c28 in _pthread_body Thread 6: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x9283de9c in JVM_NewInstance #3 0x92844e18 in JVM_GetClassLoader #4 0x92844ba4 in JVM_GetClassLoader #5 0x928a51fc in JVM_GetClassMethodsCount #6 0x90020c28 in _pthread_body Thread 7: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x9285eb40 in JVM_FillInStackTrace #4 0x92903300 in JVM_InitProperties #5 0x92903138 in JVM_InitProperties #6 0x928787a0 in JVM_FindClassFromClass #7 0x928a51fc in JVM_GetClassMethodsCount #8 0x90020c28 in _pthread_body Thread 8: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x9285eb40 in JVM_FillInStackTrace #4 0x9288890c in JVM_StartThread #5 0x92876c10 in JVM_FindLoadedClass #6 0x928787a0 in JVM_FindClassFromClass #7 0x928a51fc in JVM_GetClassMethodsCount #8 0x90020c28 in _pthread_body PPC Thread State: srr0: 0x67653a60 srr1: 0x4000d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x67653a63 ctr: 0x05018e40 mq: 0x00000000 r0: 0x67653a63 r1: 0xbfffd800 r2: 0x00000001 r3: 0x00000001 r4: 0x0108bd70 r5: 0x00000000 r6: 0x00000000 r7: 0xfd2996d0 r8: 0x00000000 r9: 0x02d6767c r10: 0x05018be8 r11: 0x009e7fb0 r12: 0x05018e40 r13: 0x00000000 r14: 0xbfffefa4 r15: 0x00000000 r16: 0xbfffec10 r17: 0x00000000 r18: 0xbffff1a0 r19: 0x00000000 r20: 0x00000001 r21: 0xbfffe650 r22: 0xbfffe640 r23: 0xbfffe740 r24: 0xbfffe720 r25: 0x02d67100 r26: 0x02d677b4 r27: 0x02d67794 r28: 0x02d67670 r29: 0x02d66f50 r30: 0x02d66f50 r31: 0x00000007 ********** Date/Time: 2004-03-26 18:13:03 -0500 OS Version: 10.2.8 (Build 6R73) Host: xxxxx-Computer.local. Command: firefox-bin PID: 354 Exception: EXC_BREAKPOINT (0x0006) Code[0]: 0x00000001Code[1]: 0x8fe01220 Thread 0 Crashed: #0 0x8fe01220 in halt #1 0x8fe10654 in link_in_need_modules #2 0x8fe10270 in bind_lazy_symbol_reference #3 0x8fe00e60 in stub_binding_helper_interface #4 0x00696948 in _ZJ11AECoreClassC4Ah #5 0x0068e810 in CreateAEHandlerClasses #6 0x00688b68 in _ZN16nsMacCommandLine10InitializeERiRPPc #7 0x0067f74c in _ZN16nsCmdLineService10InitializeEiPPc #8 0x00849b38 in _Z5main1iPPcP11nsISupportsRK12nsXREAppData #9 0x0084a5e0 in _Z8xre_mainiPPcRK12nsXREAppData #10 0x00009850 in main #11 0x000094e4 in _start (crt.c:267) #12 0x00009358 in start Thread 1: #0 0x9002568c in select #1 0x0151f77c in poll #2 0x0151bfc8 in _pr_poll_with_poll #3 0x000bde98 in _ZN24nsSocketTransportService3RunEv #4 0x0504614c in _ZN8nsThread4MainEPv #5 0x0151d410 in _pt_root #6 0x90020c28 in _pthread_body PPC Thread State: srr0: 0x8fe01220 srr1: 0x0002f030 vrsave: 0x00000000 xer: 0x20000000 lr: 0x8fe09bd8 ctr: 0x00000000 mq: 0x00000000 r0: 0x00000004 r1: 0xbffff7a0 r2: 0x8fe0b794 r3: 0x000000b4 r4: 0x00000000 r5: 0x000000b4 r6: 0x0000000a r7: 0x6e656420 r8: 0x6420746f r9: 0x00000000 r10: 0x8fe4850c r11: 0x00000006 r12: 0x8fe71adb r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0xbffffdf0 r17: 0xbffffee8 r18: 0x00000002 r19: 0xbffffb10 r20: 0x009e0000 r21: 0x009f0000 r22: 0xbffffb20 r23: 0x0509cd40 r24: 0xbffffb30 r25: 0x009e9380 r26: 0x00b867a0 r27: 0x00e644cf r28: 0x8fe4841c r29: 0x8fe484ec r30: 0x8fe484ec r31: 0x8fe0995c
.
Assignee: aaronleventhal → general
Component: Accessibility APIs → Browser-General
QA Contact: core.accessibility-apis → general
Keywords: crash
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.