Open
Bug 1626810
Opened 5 years ago
Updated 2 years ago
Component manager fails while trying to load chrome.manifest in packaged builds
Categories
(Core :: XPCOM, task, P3)
Core
XPCOM
Tracking
()
NEW
People
(Reporter: mccr8, Unassigned)
References
Details
Attachments
(1 file)
I wrote a patch to assert in various places in the component manager if they fail, including the load that happens in nsComponentManagerImpl::ManifestContract(). If I push that to try, that assert fails, with the message:
XXXX Could not read chrome manifest 'file:///builds/worker/workspace/build/tests/bin/chrome.manifest'.
This doesn't happen locally. My guess is that in a package build we're still trying to load this manifest file, but it doesn't exist in a packaged build.
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
I guess this is actually happening inside some instance of XPCShell used for some server thing during a Mochitest?
TEST-UNEXPECTED-FAIL | runtests.py | Timed out while waiting for server startup.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•