Closed
Bug 679143
Opened 14 years ago
Closed 13 years ago
Could not load inserted library/plugin crash on Mac OS X platform with Nightly 8/15/2011
Categories
(Firefox for Android Graveyard :: General, defect, P4)
Tracking
(fennec+)
RESOLVED
INCOMPLETE
| Tracking | Status | |
|---|---|---|
| fennec | + | --- |
People
(Reporter: nhirata, Unassigned)
Details
(Keywords: crash)
STR:
0. Delete any existing profiles from ~<user>/Library/Application Support/Fennec
1. install nightly build on Mac
2. launch and try to go to www.google.com
3. quit.
4. look at console and also the log in ~<user>/Library/Logs/DiagnosticReports/plugin-container_*
Expected: no plugin crash/library load errors
Actual: plugin crash/lib load error
In today's nightly build on the mac (Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv8.0a1) Gecko/20110815 Firefox/8.0a1 Fennec/8.0a1
), I'm getting a plugin-container crash:
Process: plugin-container [1509]
Path: /Users/nhirata/Desktop/Fennec.app/Contents/MacOS/plugin-container.app/Contents/MacOS/plugin-container
Identifier: plugin-container
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: fennec [1506]
Date/Time: 2011-08-15 14:17:14.729 -0700
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
could not load inserted library: /Users/nhirata/Desktop/Fennec.app/Contents/MacOS/libplugin_child_interpose.dylib
Binary Images:
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <A4F6ADCC-6448-37B4-ED6C-ABB2CD06F448> /usr/lib/dyld
One of the libraries did not seem to load according to console:
8/15/11 2:15:46 PM [0x0-0x5f05f].org.mozilla.fennec[1493] dyld: could not load inserted library: /Users/nhirata/Desktop/Fennec.app/Contents/MacOS/libplugin_child_interpose.dylib
8/15/11 2:15:56 PM [0x0-0x5f05f].org.mozilla.fennec[1493] WARNING: parent WaitForMessage() failed: 0x10004003 (ipc/rcv) timed out: file /builds/slave/m-cen-osx-mb-ntly/build/ipc/glue/GeckoChildProcessHost.cpp, line 611
| Reporter | ||
Updated•14 years ago
|
| Reporter | ||
Comment 1•14 years ago
|
||
Works = 2011-05-23-04-mozilla-central-macosx/
Busted = 2011-05-31-11-mozilla-central-macosx/
There's no Mozilla-central-MacOsX between the 23rd and the 31st.
Windows nightly does not crash: Mozilla/5.0 (Windows NT 5.1; rv:9.0a1) Gecko/20110826 Firefox/9.0a1 Fennec/9.0a1
Current MacOSX will crash:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0a1) Gecko/20110826 Firefox/9.0a1 Fennec/9.0a1
Current Linux will crash on quit for the x11 issue bug 605335:
Mozilla/5.0 (X11; Linux i686; rv9.0a1) Gecko/20110826 Firefox/9.0a1 Fennec/9.0a1
Comment 2•14 years ago
|
||
Based on Comment #1 I'm removing the regressionwindow-wanted tag.
Keywords: regressionwindow-wanted
Comment 3•14 years ago
|
||
Nominating for tracking-fennec because this makes Mac desktop builds of Fennec useless for web developers and Mozilla developers.
tracking-fennec: --- → ?
Keywords: helpwanted
Comment 4•14 years ago
|
||
who should we ping about increasing the priority of this bug? Desktop Fennec is the easiest and fastest (workflow-wise) way to jump into mobile, so having it broken is very serious.
For instance, Matteo and I were going to take a look at some mobile add-ons stuff the other day, and couldn't because of this bug.
Comment 5•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0f9347d40121&tochange=42d996c34679 is the pushlog for the range in comment 1.
Updated•14 years ago
|
tracking-fennec: ? → +
Comment 6•14 years ago
|
||
A regression range of a week isn't exactly a regression range, it'd probably be useful to narrow down this more with bisecting
Keywords: regressionwindow-wanted
(In reply to Naoki Hirata :nhirata from comment #0)
I have the same problem.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
| Reporter | ||
Comment 8•13 years ago
|
||
We no longer have desktop fennec for Native, so clearing the field.
Keywords: helpwanted,
regressionwindow-wanted
You need to log in
before you can comment on or make changes to this bug.
Description
•