The default bug view has changed. See this FAQ.

"ASSERTION: Getting architecture of plugin container failed!"

VERIFIED FIXED

Status

()

Core
IPC
VERIFIED FIXED
6 years ago
5 years ago

People

(Reporter: Jesse Ruderman, Assigned: Josh Aas)

Tracking

(4 keywords)

Trunk
x86_64
Mac OS X
assertion, testcase, verified-aurora, verified-beta
Points:
---

Firefox Tracking Flags

(firefox9 fixed)

Details

(Whiteboard: [qa!])

Attachments

(4 attachments)

(Reporter)

Description

6 years ago
Created attachment 543646 [details]
testcase

###!!! ASSERTION: Getting architecture of plugin container failed!: 'NS_SUCCEEDED(rv) && pluginContainerArchs != 0', file /Users/jruderman/trees/mozilla-central/ipc/glue/GeckoChildProcessHost.cpp, line 250
(Reporter)

Comment 1

6 years ago
Created attachment 543647 [details]
stack trace
(Reporter)

Comment 2

6 years ago
Created attachment 543648 [details]
my mozconfig
(Assignee)

Updated

6 years ago
Assignee: nobody → joshmoz
(Assignee)

Comment 3

6 years ago
The problem is that we attempt to look up the architecture on the plugin binary with a bad path:

.../NightlyDebug.app/Contents/MacOS/plugin-container.app/Contents/MacOS/plugin-container.app/Contents/MacOS/plugin-container

Note that "/Contents/MacOS/plugin-container.app" has been appended twice.
(Assignee)

Comment 4

6 years ago
Created attachment 557055 [details] [diff] [review]
fix v1.0

The assertion is coming from the child process. The problem is that we append the path to the child process bundle even if we started with the child process binary location.
Attachment #557055 - Flags: review?(benjamin)
Attachment #557055 - Flags: review?(benjamin) → review+
(Assignee)

Comment 5

6 years ago
pushed to mozilla-central

http://hg.mozilla.org/mozilla-central/rev/13b9a3f0eb42
Status: NEW → RESOLVED
Last Resolved: 6 years ago
status-firefox9: --- → fixed
Resolution: --- → FIXED
Whiteboard: [qa+]

Comment 6

5 years ago
I have verified this using the test case from the attachment on:

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20100101 Firefox/9.0 beta 4
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0a2) Gecko/20111127 Firefox/10.0a2
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0a1) Gecko/20111204 Firefox/11.0a1

The process of getting the add-on worked as expected (no add-ons were found).
This is the right functionality or I have to consider other aspects?
Can I change the status of this bug tu Verified?

Thanks.

Comment 7

5 years ago
Considering comment6, setting resolution to Verified Fixed
Status: RESOLVED → VERIFIED
Keywords: verified-aurora, verified-beta
Whiteboard: [qa+] → [qa!]
You need to log in before you can comment on or make changes to this bug.