Closed Bug 1232312 Opened 9 years ago Closed 4 years ago

Autophone - Mdm failure - dom/media/test/test_webvtt_disabled.html

Categories

(Firefox for Android Graveyard :: General, defect)

defect
Not set
normal

Tracking

(fennec+)

RESOLVED INCOMPLETE
Tracking Status
fennec + ---

People

(Reporter: bc, Assigned: esawin)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

https://treeherder.mozilla.org/#/jobs?repo=try&revision=a99d064ef982&exclusion_profile=false&selectedJob=14568919 Nexus 4 Android 4.2 >TEST-UNEXPECTED-FAIL | dom/media/test/test_webvtt_disabled.html | application ran for longer than allowed maximum time >PROCESS-CRASH | dom/media/test/test_webvtt_disabled.html | application crashed [@ libc.so + 0x17ee4] >Operating system: Android > 0.0.0 Linux 3.4.0-perf-g7ce11cd #1 SMP PREEMPT Tue Jan 29 11:41:33 PST 2013 armv7l google/occam/mako:4.2.2/JDQ39/573038:user/release-keys >CPU: arm > ARMv0 > 4 CPUs > >Crash reason: SIGABRT >Crash address: 0x54cc >Process uptime: not available > >Thread 0 (crashed) > 0 libc.so + 0x17ee4 > r0 = 0xfffffffc r1 = 0xbe9c4520 r2 = 0x00000010 r3 = 0xffffffff > r4 = 0x6e4aef08 r5 = 0xffffffff r6 = 0x00000000 r7 = 0x000000fc > r8 = 0x00000000 r9 = 0x00000014 r10 = 0x6e4aef1c r12 = 0x4034dff4 > fp = 0xbe9c4694 sp = 0xbe9c44d8 lr = 0x40348b0d pc = 0x40178ee4 > Found by: given as instruction pointer in context > 1 libbinder.so!_ZN7android6Parcel11setDataSizeEj + 0x8 > sp = 0xbe9c4510 pc = 0x40138fc1 > Found by: stack scanning > 2 libbinder.so!_ZN7android14IPCThreadState14talkWithDriverEb + 0xd4 > r3 = 0x0000002c r4 = 0x40377220 r5 = 0x0000002c sp = 0xbe9c4520 > lr = 0x40135bf3 pc = 0x40135bf3 > Found by: call frame info > 3 libbinder.so!_ZN7android14IPCThreadState15waitForResponseEPNS_6ParcelEPi + 0x4e > r4 = 0x00000000 r5 = 0x403771f0 r6 = 0x00000000 r7 = 0x00000000 > r8 = 0x00000000 sp = 0xbe9c4550 lr = 0x401360c1 pc = 0x401360c1 > Found by: call frame info
tracking-fennec: --- → ?
Assignee: nobody → esawin
tracking-fennec: ? → +
See Also: → 1153860
TEST_UNEXPECTED_FAIL | autophone-mochitest-dom-media | Test exited with return code 1 TEST-TIMEOUT | dom/media/test/test_webvtt_disabled.html | application timed out after 330 seconds with no output PROCESS-CRASH | dom/media/test/test_webvtt_disabled.html | application crashed [@ libc.so + 0x17ee4] See https://treeherder.mozilla.org/#/jobs?repo=fx-team&revision=3488451848ce&exclusion_profile=false&filter-tier=1&filter-tier=2&filter-tier=3&filter-searchStr=autophone
The test itself passes and finishes (see GeckoDump log), but then we wail to shutdown Fennec which results in a timeout-abort. This also reproduces with the test semantics reversed: https://treeherder.mozilla.org/#/jobs?repo=try&revision=449de761ac70&filter-tier=1&filter-tier=2&filter-tier=3&exclusion_profile=false And with a completely empty test: https://treeherder.mozilla.org/#/jobs?repo=try&revision=76c75315a5b6&filter-tier=1&filter-tier=2&filter-tier=3&exclusion_profile=false The reason why the timeout is attributed to this particular test is because it is the last test in the chunk. Do we know why we might fail to shutdown Fennec after all tests have finished?
s/wail/fail in comment 2
By disabling test_webvtt_disabled, the timeout is moved to the new last test in chunk (test_vttparser): https://treeherder.mozilla.org/#/jobs?repo=try&revision=a930e46ca392&exclusion_profile=false&filter-tier=1&filter-tier=2&filter-tier=3&selectedJob=18786788
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.