Closed
Bug 640924
Opened 14 years ago
Closed 6 years ago
Cannot create cryptohash object in out-of-process chrome
Categories
(Firefox for Android Graveyard :: Extension Compatibility, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mozilla, Unassigned)
References
Details
Attachments
(1 file)
2.72 KB,
application/x-xpinstall
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-AU; rv:1.9.2.14) Gecko/20110221 Ubuntu/10.10 (maverick) Firefox/3.6.14
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b13pre) Gecko/20110310 Firefox/4.0b13pre Fennec/4.0b6pre
in the out-of-process chrome context, the cryptohash object cannot be initialised. The error as reported in the error console is:
NS_ERROR_XPC_CI_RETURNED_FAILURE: Component returned failure code: 0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE) [nsIJSCID.createInstance]
Reproducible: Always
Steps to Reproduce:
1. download test addon
2. install test addon
3. open new tab
Actual Results:
Error got logged in error console
Expected Results:
Nothing
Reporter | ||
Comment 1•14 years ago
|
||
Comment 2•14 years ago
|
||
Unfortunately we don't allow creating components in content processes that require NSS to be initialized. You'll need to create it in chrome and send messages back and forth use make use of the object.
Comment 3•14 years ago
|
||
There are some movements to make hashing independent on (unimplemented by) NSS. This is probably tracked in bug 611781, but I'm not 100% sure it is the one. Anyway, this is not going to happen very soon.
Comment 4•13 years ago
|
||
Issue is reproducible on Nightly /14.0a1 XUL 2012-03-29 on HTC Desire Z
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → Android
Hardware: x86 → ARM
Comment 5•6 years ago
|
||
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•