Closed
Bug 1299653
Opened 5 years ago
Closed 4 years ago
Intermittent toolkit/components/narrate/test/browser_narrate_disable.js | Found a tab after previous test timed out: about:blank | Assertion failure: aCode == MsgDropped (Processing error in CompositorBridgeChild), at ipc/CompositorBridgeChild.cpp:1066
Categories
(Core :: IPC, defect, P3)
Core
IPC
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: intermittent-bug-filer, Unassigned)
References
Details
(Keywords: intermittent-failure)
Attachments
(1 file)
Filed by: wkocher [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=2862983&repo=autoland https://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-win32-debug/1472662281/autoland_win7_vm-debug_test-mochitest-e10s-browser-chrome-2-bm140-tests1-windows-build39.txt.gz
Updated•5 years ago
|
Component: General → IPC
Product: Toolkit → Core
Comment 1•5 years ago
|
||
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Updated•5 years ago
|
Flags: needinfo?(eitan)
Updated•5 years ago
|
status-firefox50:
--- → affected
status-firefox51:
--- → affected
Updated•5 years ago
|
Assignee: nobody → eitan
Flags: needinfo?(eitan)
Comment 2•5 years ago
|
||
From the stack, this looks like a layout issue. I think the tab is closed mid-scroll and some IPC messages get missed. I can probably remedy this test by guaranteeing we are not scrolling by the end of it..
Comment hidden (mozreview-request) |
Comment hidden (Intermittent Failures Robot) |
Comment 5•5 years ago
|
||
(In reply to Eitan Isaacson [:eeejay] from comment #2) > From the stack, this looks like a layout issue. I think the tab is closed > mid-scroll and some IPC messages get missed. > > I can probably remedy this test by guaranteeing we are not scrolling by the > end of it.. Can this case happen in actual browser usage?
Comment 6•5 years ago
|
||
(In reply to Jed Davis [:jld] {⏰UTC-6} from comment #5) > (In reply to Eitan Isaacson [:eeejay] from comment #2) > > From the stack, this looks like a layout issue. I think the tab is closed > > mid-scroll and some IPC messages get missed. > > > > I can probably remedy this test by guaranteeing we are not scrolling by the > > end of it.. > > Can this case happen in actual browser usage? I'm assuming so. To clarify this is an assertion failure in debug builds, not an actual segmentation fault.
Comment 7•5 years ago
|
||
mozreview-review |
Comment on attachment 8787913 [details] Bug 1299653 - Don't have the page scrolling when the tab is closed. https://reviewboard.mozilla.org/r/76504/#review75180
Attachment #8787913 -
Flags: review?(jaws) → review+
Pushed by eisaacson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4266dca3ab7d Don't have the page scrolling when the tab is closed. r=jaws
Comment 9•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4266dca3ab7d
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
Comment 10•5 years ago
|
||
bugherderuplift |
https://hg.mozilla.org/releases/mozilla-aurora/rev/170d7f1c6661
Comment 11•5 years ago
|
||
This is still failing.
Status: RESOLVED → REOPENED
Flags: needinfo?(eitan)
Resolution: FIXED → ---
Target Milestone: mozilla51 → ---
Comment 12•5 years ago
|
||
Wouldn't orange robot be posting here? Any links to failed tests?
Comment 13•5 years ago
|
||
It only posts in bugs above a certain threshold. https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1299653
Comment 14•5 years ago
|
||
David, I tried working around this assertion, but looks like I failed. Do you have any clue why we are running into this?
Flags: needinfo?(eitan) → needinfo?(dvander)
We're hitting this case here [1], which means an async message's callback returned false. However CompositorBridgeChild doesn't have any methods which actually do that, so probably it was a routing or channel state problem, which would get deduced here [2]. To narrow down which case, I would log the message code in CompositorBridgeChild::OnProcessingError. You could also log the message ID in MessageChannel::DispatchAsyncMessage, which we'd want to know if this is a send-after-shutdown bug. [1] http://searchfox.org/mozilla-central/rev/950e13cca1fda6507dc53c243295044e8eda4493/ipc/glue/MessageChannel.cpp#1664 [2] http://searchfox.org/mozilla-central/source/__GENERATED__/ipc/ipdl/PCompositorBridgeChild.cpp#1246
Flags: needinfo?(dvander)
Updated•5 years ago
|
Assignee: eitan → nobody
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 20•4 years ago
|
||
resolving this as we haven't seen it in almost a year.
Status: REOPENED → RESOLVED
Closed: 5 years ago → 4 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•