Closed Bug 216289 Opened 22 years ago Closed 22 years ago

20030814 latest nightly crashes on launch

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 216275

People

(Reporter: mike+bugzilla, Assigned: mikepinkerton)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/85 (KHTML, like Gecko) Safari/85 Build Identifier: nightly build, dated 14 Aug 2003 07:39:27 GMT (20030814) 10.2.6, iBook 500MHz 384MB, Camino nightly 20030814: crashes on launch in CHBrowserView initWithFrame. Reproducible: Always Steps to Reproduce: 1. download 20030814 nightly build of Camino 2. install in /Applications 3. launch Actual Results: crash in CHBrowserView initWithFrame. Reproduced on an imac 500MHz 768MB, also running 10.2.6. Will attach crash log.
Attached file crash log
I see that the crash log (attached) has some lines like: Thread 1: #0 0x90073c28 in mach_msg_trap #1 0x90005f70 in mach_msg #2 0xc0009190 in __ape_internal #3 0xc0000efc in __ape_agent #4 0x90020d28 in _pthread_body That might point to Unsanity's APE software, so I moved the Application Enhancer framework out of my /Library/Frameworks, logged out, logged back in, and repeated the test. Camino still crashed in: Thread 0 Crashed: #0 0x0001718c in -[CHBrowserView initWithFrame:] #1 0x0001709c in -[CHBrowserView initWithFrame:andWindow:] #2 0x00004f64 in -[BrowserWrapper initWithFrame:] #3 0x00004e98 in -[BrowserWrapper initWithTab:andWindow:] But this time there was no Thread 1 and no ape-related traceback. So I think that rules out any Unsanity interaction.
*** This bug has been marked as a duplicate of 216275 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: