1477891 - Intermittent /service-workers/service-worker/windowclient-navigate.https.html | application crashed [@ mozalloc_abort]

Status: RESOLVED INCOMPLETE

(Core :: DOM: Service Workers, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: cbrindusan [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=189682663&repo=mozilla-inbound

https://queue.taskcluster.net/v1/task/QeYyPnW0TEmsruADMAgq7A/runs/0/artifacts/public/logs/live_backing.log

[task 2018-07-24T01:37:17.513Z] 01:37:17     INFO - TEST-START | /service-workers/service-worker/windowclient-navigate.https.html
[task 2018-07-24T01:37:17.590Z] 01:37:17     INFO - PID 15272 | 1532396237579	Marionette	DEBUG	[2147484977] Frame script loaded
[task 2018-07-24T01:37:17.594Z] 01:37:17     INFO - PID 15272 | 1532396237589	Marionette	DEBUG	[2147484977] Frame script registered
[task 2018-07-24T01:37:18.088Z] 01:37:18     INFO - PID 15272 | ###!!! [Parent][DispatchAsyncMessage] Error: PClientSourceOp::Msg___delete__ Route error: message sent to unknown actor ID
[task 2018-07-24T01:37:18.493Z] 01:37:18     INFO - PID 15272 | Sandbox: Unexpected EOF, op 0 flags 00 path /dev/urandom
[task 2018-07-24T01:37:18.493Z] 01:37:18     INFO - PID 15272 | [Child 15338, DOM Worker] ###!!! ABORT: file /builds/worker/workspace/build/src/ipc/chromium/src/base/rand_util_posix.cc, line 21
[task 2018-07-24T01:37:18.494Z] 01:37:18     INFO - PID 15272 | [Child 15338, DOM Worker] ###!!! ABORT: file /builds/worker/workspace/build/src/ipc/chromium/src/base/rand_util_posix.cc, line 21
[task 2018-07-24T01:37:18.712Z] 01:37:18     INFO - PID 15272 | ###!!! [Parent][MessageChannel] Error: (msgtype=0x17007E,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
[task 2018-07-24T01:37:18.713Z] 01:37:18     INFO - PID 15272 | ###!!! [Parent][MessageChannel] Error: (msgtype=0x17007E,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
[task 2018-07-24T01:37:18.713Z] 01:37:18     INFO - PID 15272 | ###!!! [Parent][MessageChannel] Error: (msgtype=0x17007E,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
[task 2018-07-24T01:37:18.810Z] 01:37:18     INFO - PID 15272 | A content process crashed and MOZ_CRASHREPORTER_SHUTDOWN is set, shutting down
[task 2018-07-24T01:37:18.947Z] 01:37:18     INFO - mozcrash Downloading symbols from: https://queue.taskcluster.net/v1/task/BPRqwvJhQ2y0fszUuudR7A/artifacts/public/build/target.crashreporter-symbols.zip
[task 2018-07-24T01:37:19.126Z] 01:37:19     INFO - PID 15272 | 1532396239115	Marionette	INFO	Stopped listening on port 2828
[task 2018-07-24T01:37:25.040Z] 01:37:25     INFO - mozcrash Copy/paste: /usr/local/bin/linux64-minidump_stackwalk /tmp/tmp2wCQE_.mozrunner/minidumps/19752249-5f78-5589-6eaf-5a0f2d4dac6c.dmp /tmp/tmpgaDgSx
[task 2018-07-24T01:37:34.252Z] 01:37:34     INFO - mozcrash Saved minidump as /builds/worker/workspace/build/blobber_upload_dir/19752249-5f78-5589-6eaf-5a0f2d4dac6c.dmp
[task 2018-07-24T01:37:34.252Z] 01:37:34     INFO - mozcrash Saved app info as /builds/worker/workspace/build/blobber_upload_dir/19752249-5f78-5589-6eaf-5a0f2d4dac6c.extra
[task 2018-07-24T01:37:34.380Z] 01:37:34     INFO - PROCESS-CRASH | /service-workers/service-worker/windowclient-navigate.https.html | application crashed [@ mozalloc_abort]

Comment 1

[meck93]

Dear Reader,

We are a joint research team from the University of Zurich, Switzerland* and Mozilla** and are building a tool to automatically recognize the type of an intermittent-failure, such as the one here.

By automatically recognizing the type of failure, the tool should provide a starting point for the bug fixing process. To evaluate and improve the tool, we kindly ask your feedback.
    
Tool Result - this intermittent-failure is most likely affected by a:
Concurrency Issue: This includes tests in which failures occur due to thread management issues (different threads or their outcomes depending on an implicit ordering), race conditions and/or deadlocks, and issues related to an asynchronous waits (e.g. a process trying to access an external resource or continuing before the external resource is available).

Feedback: 
1. Did the tool correctly recognize the type of intermittent-failure? (please also explain why or why not)
2. Did the information from the tool help your analysis, the bug fixing process, or anything in the process? (please also let us know how the tool was useful and/or what would improve the tool's usefulness for you)

Thank you very much for your help! 
*Moritz, Fabio and Alberto (http://www.ifi.uzh.ch/en/zest/team.html)
**Marco Castellucio (https://marco-c.github.io/)

Comment 2

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup