Closed Bug 1525670 Opened 4 years ago Closed 4 years ago

windows/aarch64 - dom/ipc/tests/test_process_error.xul | application terminated with exit code 3221226505

Categories

(Core :: DOM: Content Processes, defect, P5)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

#[markdown(off)]
Filed by: egao [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=226341281&repo=try

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

Failure encountered as part of running mochitest-chrome suite on win10/aarch64.

data from the log:
12:27:00 INFO - TEST-START | dom/ipc/tests/test_JSWindowActor.xul
12:27:01 INFO - GECKO(10644) | MEMORY STAT | vsize 5931MB | vsizeMaxContiguous 68528948MB | residentFast 309MB | heapAllocated 106MB
12:27:01 INFO - TEST-OK | dom/ipc/tests/test_JSWindowActor.xul | took 1128ms
12:27:01 INFO - TEST-START | dom/ipc/tests/test_process_error.xul
12:27:02 INFO - GECKO(10644) | Et tu, Brute?
12:27:02 INFO - TEST-INFO | Main app process: exit c0000409
12:27:02 INFO - Buffered messages finished
12:27:02 ERROR - TEST-UNEXPECTED-FAIL | dom/ipc/tests/test_process_error.xul | application terminated with exit code 3221226505
12:27:02 INFO - runtests.py | Application ran for: 0:00:05.614000
12:27:02 INFO - zombiecheck | Reading PID log: c:\users\testdr~1\appdata\local\temp\tmpwx8ooqpidlog
12:27:02 INFO - ==> process 848 launched child process 10044 ("C:\tasks\task_1549455158\build\application\firefox\firefox.exe" -contentproc --channel="848.0.871252707\869049900" -childID 1 -isForBrowser -prefsHandle 4144 -prefMapHandle 3068 -prefsLen 1 -prefMapSize 200744 -parentBuildID 20190205155112 -greomni "C:\tasks\task_1549455158\build\application\firefox\omni.ja" -appomni "C:\tasks\task_1549455158\build\application\firefox\browser\omni.ja" -appdir "C:\tasks\task_1549455158\build\application\firefox\browser" - 848 "\.\pipe\gecko-crash-server-pipe.848" 4140 tab)
12:27:02 INFO - zombiecheck | Checking for orphan process with PID: 10044
12:27:02 INFO - Stopping web server
12:27:02 INFO - Stopping web socket server
12:27:02 INFO - Stopping ssltunnel

here is a link to the test caes:
https://searchfox.org/mozilla-central/source/dom/ipc/tests/test_process_error.xul

and this is a case where we have |skip-if = !crashreporter|

Summary: TEST-UNEXPECTED-FAIL | dom/ipc/tests/test_process_error.xul | application terminated with exit code 3221226505 → windows/aarch64 - dom/ipc/tests/test_process_error.xul | application terminated with exit code 3221226505

Try run: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&revision=af9472de86459eb65f95a2eeb6d47848a824a610

As of mozilla-central revision 78601ca the mochitest-chrome-2 test run is reporting green.

20:28:17     INFO - TEST-START | dom/ipc/tests/test_process_error.xul
20:28:17     INFO - GECKO(7644) | Et tu, Brute?
20:28:18     INFO - GECKO(7644) | ###!!! [Parent][MessageChannel] Error: (msgtype=0x1E009A,name=PBrowser::Msg_UpdateNativeWindowHandle) Channel error: cannot send/recv
20:28:18     INFO - GECKO(7644) | ###!!! [Parent][MessageChannel] Error: (msgtype=0x1E0089,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
20:28:18     INFO - GECKO(7644) | ###!!! [Parent][MessageChannel] Error: (msgtype=0x34003E,name=PContent::Msg_NotifyProcessPriorityChanged) Channel error: cannot send/recv
20:28:18     INFO - GECKO(7644) | MEMORY STAT | vsize 5924MB | vsizeMaxContiguous 67592258MB | residentFast 285MB | heapAllocated 95MB
20:28:18     INFO - GECKO(7644) | [Parent 7980, Gecko_IOThread] WARNING: file z:/build/build/src/ipc/chromium/src/base/process_util_win.cc, line 160
20:28:19     INFO - TEST-OK | dom/ipc/tests/test_process_error.xul | took 2382ms
20:28:19     INFO - TEST-START | Shutdown
20:28:19     INFO - Passed:  21
20:28:19     INFO - Failed:  0
20:28:19     INFO - Todo:    0
20:28:20     INFO - Mode:    non-e10s
20:28:20     INFO - Slowest: 2382ms - chrome://mochitests/content/chrome/dom/ipc/tests/test_process_error.xul

Closing this bug as resolved.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.