Closed
Bug 244518
Opened 21 years ago
Closed 21 years ago
Firefox AVIARY_BRANCH build crashes at startup
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 244304
People
(Reporter: MMx, Assigned: bugzilla)
Details
(Keywords: crash)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040519 Firefox/0.8.0+ (MMx2000)
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040524 Firefox/0.8.0+ (MMx2000)
this morning I pulled the AVIARY-branch from CVS (0830 UTC) and build it on my
MacOS 10.3.3 using default+O2+disable-debug+disable-tests. (clobber build)
When I try to launch this build *without* any browser profile available, it
crashes instantly, not producing a crashlog.
If I got a Seamonkey profile, it imports the profile and crashes then, creating
a crashlog.
On any further launch, it crashed instantly again.
Reproducible: Always
Steps to Reproduce:
1. build Firefox AVIARY_1_0_20040515_BRANCH from CVS
2. launch it
Actual Results:
Dock icon bounces and disappears again.
Expected Results:
Firefox should start normally
Extract from the crashlog:
Thread 0 Crashed:
0 libgklayout.dylib 0x022aaa84
GlobalWindowImpl::SetNewDocument(nsIDOMDocument*, int, int) + 0x5b4
1 libgklayout.dylib 0x0214b578 DocumentViewerImpl::Close() + 0x8c
2 libdocshell.dylib 0x007a1da8 nsDocShell::Destroy() + 0x124
3 libdocshell.dylib 0x007ae4fc nsWebShell::Destroy() + 0x18
4 libnsappshell.dylib 0x013e90f8 nsXULWindow::Destroy() + 0x2dc
5 libnsappshell.dylib 0x013f8044 nsWebShellWindow::Destroy() + 0x288
6 libnsappshell.dylib 0x013f2ee8 nsAppShellService::Observe(nsISupports*,
char const*, unsigned short const*) + 0x438
7 libxpcom.dylib 0x00373e64
nsObserverService::NotifyObservers(nsISupports*, char const*, unsigned short
const*) + 0x10c
8 libxpcom.dylib 0x0036bf74 NS_ShutdownXPCOM + 0xdc
9 org.mozilla.firefox 0x0000a96c ScopedXPCOMStartup::~ScopedXPCOMStartup
[unified]() + 0xd0
10 org.mozilla.firefox 0x0000ca84 xre_main(int, char**, nsXREAppData const*) +
0x844
11 org.mozilla.firefox 0x00008ab4 _start + 0x188 (crt.c:267)
12 org.mozilla.firefox 0x00008928 start + 0x30
Reporter | ||
Comment 1•21 years ago
|
||
the complete crash log of the crash described above
Reporter | ||
Comment 2•21 years ago
|
||
fixed typo in summary
Summary: Firefox AVIARY_BRANCH build crashed at startup → Firefox AVIARY_BRANCH build crashes at startup
Reporter | ||
Comment 3•21 years ago
|
||
sometimes, there is the following console output:
Firefox.app/Contents/MacOS/firefox-bin: can't map file: /Library/Internet
Plug-Ins/Java Applet.plugin ((os/kern) invalid argument)
*** loading the extensions datasource
Reporter | ||
Comment 4•21 years ago
|
||
additional crash logs, created under MacOS X 10.2.8. There are also console
outputs that might point to a possible problem with OS X 10.2.x (undefined
symbols)
1. crash:
/Users/martin/Desktop/Firefox.app/Contents/MacOS/firefox-bin: can't map file:
/Users/martin/Desktop/Firefox.app/Contents/MacOS/plugins/Default Plugin.plugin
((os/kern) invalid argument)
dyld: /Users/martin/Desktop/Firefox.app/Contents/MacOS/firefox-bin Undefined
symbols:
/Users/martin/Desktop/Firefox.app/Contents/MacOS/components/libgfx_mac.dylib
undefined reference to _PR_Realloc expected to be defined in Carbon
May 24 18:46:50 Maxwell crashdump: Crash report written to:
/Users/martin/Library/Logs/CrashReporter/firefox-bin.crash.log
2. crash:
*** loading the extensions datasource
dyld: /Users/martin/Desktop/Firefox.app/Contents/MacOS/firefox-bin Undefined
symbols:
/Users/martin/Desktop/Firefox.app/Contents/MacOS/components/libgfx_mac.dylib
undefined reference to _PR_Realloc expected to be defined in Carbon
May 24 18:48:26 Maxwell crashdump: Crash report written to:
/Users/martin/Library/Logs/CrashReporter/firefox-bin.crash.log
I think this is really a dup of bug 244304... more of less... anyone else?
Reporter | ||
Comment 6•21 years ago
|
||
As Riscky and I have found out, the current nighties availiable at mozilla.org
are in fact AVIARY-builds, so this *is* a dupe of bug #244304
*** This bug has been marked as a duplicate of 244304 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•19 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•