Open Bug 1544641 Opened 5 years ago Updated 2 years ago

WPT on Geckoview frequently crashes in /html/webappapis/dynamic-markup-insertion/opening-the-input-stream/tasks.window.js.ini

Categories

(Core :: DOM: Core & HTML, defect, P2)

Product:
Core
Component:
DOM: Core & HTML
Platform:
Unspecified
Android
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox68 --- affected

People

(Reporter: KWierso, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [geckoview:p2])

I'm trying to get web-platform-tests running against Geckoview's test runner activity, and I'm seeing some frequent (but not necessarily permanent) crashes during this html/webappapis test. I can try to mark it as expected crashes to green up the test runs, but figured I should file a bug to track actually fixing the crashes.

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

Is there a crash stack for this? (I failed to find one in the log.)

Flags: needinfo?(wkocher)
Priority: -- → P2

I'm not seeing any. Either I'm not looking for them in the right place, I haven't configured geckoview correctly to generate them, or they just aren't getting generated. I needinfo'd one of the mobile devs in the meta bug asking what's going on, hopefully he can help.

Flags: needinfo?(wkocher)

(In reply to Wes Kocher (:KWierso) from comment #0)

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

I don't think this was an actual crash.

https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=239543653&repo=try&lineNumber=4063

[task 2019-04-11T02:48:00.376Z] 02:48:00 INFO - IOError on command, setting status to CRASH
[task 2019-04-11T02:48:00.376Z] 02:48:00 INFO - TEST-UNEXPECTED-CRASH | /html/webappapis/dynamic-markup-insertion/opening-the-input-stream/tasks.window.html | expected TIMEOUT

https://taskcluster-artifacts.net/SHDjX4K3R_uB3xMY_psXPw/0/public/test_info//logcat-emulator-5554.log

04-11 03:41:42.630 9877 9918 I Gecko : IPDL protocol error: Handler returned error code!
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : IPDL protocol error: Handler returned error code!
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : IPDL protocol error: Handler returned error code!
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : IPDL protocol error: Handler returned error code!
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : IPDL protocol error: Handler returned error code!
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:41:42.630 9877 9918 I Gecko : ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
04-11 03:41:42.630 9877 9918 I Gecko :
04-11 03:42:10.940 9877 9893 E GeckoConsole: [JavaScript Error: "Polling for changes failed: NetworkError when attempting to fetch resource.." {file: "resource://services-settings/remote-settings.js" line: 208}]
04-11 03:42:10.940 9877 9893 E GeckoConsole: remoteSettingsFunction/remoteSettings.pollChanges@resource://services-settings/remote-settings.js:208:13
04-11 03:44:00.520 1311 1324 I UsageStatsService: User[0] Flushing usage stats to disk
04-11 03:47:43.540 10008 10008 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
04-11 03:47:43.540 10008 10008 D AndroidRuntime: CheckJNI is ON
04-11 03:47:43.560 10008 10008 W art : Unexpected CPU variant for X86 using defaults: x86_64
04-11 03:47:43.560 10008 10008 D ICU : No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat
04-11 03:47:43.570 10008 10008 E memtrack: Couldn't load memtrack module (No such file or directory)
04-11 03:47:43.570 10008 10008 E android.os.Debug: failed to load memtrack module: -2
04-11 03:47:43.570 10008 10008 I Radio-JNI: register_android_hardware_Radio DONE
04-11 03:47:43.570 10008 10008 D AndroidRuntime: Calling main entry com.android.commands.am.Am
04-11 03:47:43.570 1311 1572 I ActivityManager: Force stopping org.mozilla.geckoview.test appid=10062 user=0: from pid 10008
04-11 03:47:43.570 1311 1572 I ActivityManager: Killing 9943:org.mozilla.geckoview.test:tab/u0a62 (adj 0): stop org.mozilla.geckoview.test
04-11 03:47:43.570 1311 1572 D ActivityManager: cleanUpApplicationRecord -- 9943
04-11 03:47:43.570 1311 1572 W ActivityManager: Scheduling restart of crashed service org.mozilla.geckoview.test/org.mozilla.gecko.process.GeckoServiceChildProcess$tab in 1000ms
04-11 03:47:43.580 1311 1572 I ActivityManager: Killing 9877:org.mozilla.geckoview.test/u0a62 (adj 0): stop org.mozilla.geckoview.test
04-11 03:47:43.580 1311 1572 D ActivityManager: cleanUpApplicationRecord -- 9877

After the IPDL errors, there is not much activity for pid 9877, but it remains alive for another 5.5 minutes until org.mozilla.geckoview.test is stopped, presumably by the harness. There is no breakpad logging either. So, no crash, no minidump, no crash report.

"IOError on command, setting status to CRASH" comes from

https://searchfox.org/mozilla-central/rev/d33d470140ce3f9426af523eaa8ecfa83476c806/testing/web-platform/tests/tools/wptrunner/wptrunner/executors/executormarionette.py#613

so...why was there an IOError in the harness?

Whiteboard: [geckoview]
status-firefox68: --- → affected
OS: Unspecified → Android
Whiteboard: [geckoview] → [geckoview:p2]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.