Closed
Bug 1046426
Opened 9 years ago
Closed 9 years ago
[e10s] Crash when using "ScrapBook" add-on's DOM Eraser: Assertion (!DispatchingUrgentMessage()) failed. sync messages forbidden while handling urgent message
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1010737
People
(Reporter: alice0775, Unassigned)
References
Details
(Keywords: addon-compat, crash)
Crash Data
Tab crashed when click a page using bp-f54a9d53-0ad2-4540-b554-d43ec2140730 Steps To Reproduce: 1. Enabled e10s autostart 2. Install ScrapBook 1.5.9 https://addons.mozilla.org/en-US/firefox/addon/scrapbook/ And restart 3. Open https://www.mozilla.org/en-US/firefox/help/ 4. Alt, select ScrapBook > Save Page As... 5. Save 6. Alt, select ScrapBook > Firefox Help (which is saved at step 5) 7. Click "DOM Eraser" icon at the bottom toolbar 8. Click one of a topic conainer to remove 9. Repeat step 8 if necessary Actual Results: Tab crashed Expected Results: No crash:
Comment 1•9 years ago
|
||
###!!! [MessageChannel][Child][/builds/slave/m-cen-osx64-ntly-0000000000000/build/ipc/glue/MessageChannel.cpp:585] Assertion (!DispatchingUrgentMessage()) failed. sync messages forbidden while handling urgent message MessageChannel 'backtrace': [(0) in async ???(actor=2) ] [(1) out async PJavaScript::Msg_CallOrConstruct(actor=-4) ] [(2) out sync PBrowser::Msg_GetInputContext(actor=2) ] remote Interrupt stack guess: 0 deferred stack size: 0 out-of-turn Interrupt replies stack size: 0 Pending queue size: 0, front to back: [Child 32884] ###!!! ABORT: sync messages forbidden while handling urgent message: file /builds/slave/m-cen-osx64-ntly-0000000000000/build/ipc/glue/MessageChannel.cpp, line 1739
Blocks: 899758
Mentor: cpeterson
status-firefox33:
--- → wontfix
status-firefox34:
--- → affected
tracking-e10s:
--- → ?
Keywords: crash
Summary: [e10s] Tab crashed when using DOM Eraser of "ScrapBook" add-on → [e10s] Crash when using "ScrapBook" add-on's DOM Eraser: Assertion (!DispatchingUrgentMessage()) failed. sync messages forbidden while handling urgent message
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•