Closed Bug 1194536 Opened 9 years ago Closed 9 years ago

Intermittent fetch-request-xhr.https.html | application crashed [@ mozilla::dom::MessagePortChild::RecvReceiveData(nsTArray<mozilla::dom::MessagePortMessage>&&)]

Categories

(Core :: DOM: Service Workers, defect)

Product:
Core
Component:
DOM: Service Workers
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla43
Tracking Flags:
Tracking Status
firefox41 --- unaffected
firefox42 --- unaffected
firefox43 --- fixed
firefox-esr38 --- unaffected

People

(Reporter: KWierso, Assigned: catalinb)

References

Details

(Keywords: intermittent-failure)

Fallout from bug 1193133, which I'll be backing out shortly.
Assignee: nobody → catalin.badea392
Blocks: 1193133
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox41: --- → unaffected
status-firefox42: --- → unaffected
status-firefox43: --- → fixed
status-firefox-esr38: --- → unaffected
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
(In reply to Treeherder Robot from comment #15) > log: > https://treeherder.mozilla.org/logviewer.html#?repo=mozilla- > inbound&job_id=12954993 > repository: mozilla-inbound > start_time: 2015-08-17T15:32:14 > who: wkocher[at]mozilla[dot]com > machine: tst-linux64-spot-250 > buildname: Ubuntu VM 12.04 x64 mozilla-inbound debug test > web-platform-tests-8 > revision: 2843215083ea > > PROCESS | 1856 | Assertion failure: mPort, at > /builds/slave/m-in-l64-d-0000000000000000000/build/src/dom/messagechannel/ > MessagePortChild.cpp:34 > PROCESS-CRASH | > /_mozilla/service-workers/service-worker/fetch-response-xhr.https.html | > application crashed [@ > mozilla::dom::MessagePortChild::RecvReceiveData(nsTArray<mozilla::dom:: > MessagePortMessage>&&)] > TEST-UNEXPECTED-CRASH | > /_mozilla/service-workers/service-worker/fetch-response-xhr.https.html | > expected TIMEOUT > Return code: 1 Andreas, can you please have a look at this? Thanks.
Status: RESOLVED → REOPENED
Flags: needinfo?(amarchesini)
Resolution: FIXED → ---
Actually, looking closer, this is in a different test than this bug was filed for, so it might be a completely new issue. I've filed bug 1195584 for this new case.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Flags: needinfo?(amarchesini)
You need to log in before you can comment on or make changes to this bug.