Closed
Bug 1252204
Opened 8 years ago
Closed 7 years ago
[e10s] Custom implementation of nsIURI + nsIURIWithPrincipal crashes in mozilla::ipc::SerializeURI
Categories
(Firefox :: Extension Compatibility, defect, P4)
Firefox
Extension Compatibility
Tracking
()
RESOLVED
INCOMPLETE
| Tracking | Status | |
|---|---|---|
| e10s | + | --- |
People
(Reporter: bugzilla.mozilla.org, Unassigned)
References
Details
(Keywords: crash, reproducible, Whiteboard: triaged)
Crash Data
Attachments
(1 file)
|
72.03 KB,
application/x-xpinstall
|
Details |
1. install attached addon 2. open addons -> ipfs gateway redirect -> options 3. disable "use custom gateway" 4. enable "keep fs: in the URL bar" 5. open the following URI in a new tab: fs:/ipfs/QmYHNYAaYK5hm3ZhZFx5W9H6xydKDGimjdgJMrMSdnctEm This works with e10s off, crashes the content process with e10s on. crash report: bp-7e6f3272-8517-4663-adff-adfa92160229 Based on discussion in bug 1247529 this seems to be due to IPC-serialization of nsIURI not being supported. But if one wants to use nsIURIWithPrincipal one must also implement nsIURI. The motivation for using nsIURIWithPrincipal is to provide fixed origins based on path elements for an authority-less URI scheme.
Blocks: e10s-addons
Blocks: e10s
Severity: normal → critical
Crash Signature: [@ mozilla::ipc::SerializeURI ]
Keywords: crash,
reproducible
Summary: [e10s] Custom implementation of nsIURI + nsIURIWithPrincipal crashes → [e10s] Custom implementation of nsIURI + nsIURIWithPrincipal crashes in mozilla::ipc::SerializeURI
|
||
Updated•8 years ago
|
tracking-e10s:
--- → +
|
||
Comment 1•8 years ago
|
||
add-on in example has few users - prioritizing high utilization work first to benefit most users the quickest possible. would take patches.
Priority: -- → P4
Whiteboard: triaged
|
||
Comment 2•7 years ago
|
||
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•