Closed Bug 1008422 Opened 11 years ago Closed 10 years ago

Intermittent Android 2.2 crashtest/reftest/jsreftest TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ryanvm, Unassigned)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=39387392&tree=Mozilla-Central Android 2.2 Tegra mozilla-central opt test crashtest on 2014-05-09 13:54:17 PDT for push 1f4ae9fdfca8 slave: tegra-329 REFTEST TEST-START | http://10.26.84.7:30329/tests/xpcom/string/crashtests/395651-1.html REFTEST TEST-LOAD | http://10.26.84.7:30329/tests/xpcom/string/crashtests/395651-1.html | 2645 / 2646 (99%) REFTEST TEST-PASS | http://10.26.84.7:30329/tests/xpcom/string/crashtests/395651-1.html | (LOAD ONLY) REFTEST INFO | Loading a blank page REFTEST TEST-END | http://10.26.84.7:30329/tests/xpcom/string/crashtests/395651-1.html REFTEST FINISHED: Slowest test took 21304ms (http://10.26.84.7:30329/tests/layout/base/crashtests/500467-1.html) REFTEST INFO | Result summary: REFTEST INFO | Successful: 2541 (2 pass, 2539 load only) REFTEST INFO | Unexpected: 0 (0 unexpected fail, 0 unexpected pass, 0 unexpected asserts, 0 unexpected fixed asserts, 0 failed load, 0 exception) REFTEST INFO | Known problems: 106 (0 known fail, 0 known asserts, 0 random, 106 skipped, 0 slow) REFTEST INFO | Total canvas count = 2 REFTEST TEST-START | Shutdown TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output INFO | automation.py | Application ran for: 0:19:49.956866 INFO | zombiecheck | Reading PID log: /tmp/tmpi8IgaPpidlog Contents of /data/anr/traces.txt: WARNING | leakcheck | refcount logging is off, so leaks can't be detected! REFTEST INFO | runreftest.py | Running tests: end.
Summary: Intermittent Android 2.2 crashtest TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output → Intermittent Android 2.2 crashtest/reftest/jsreftest TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output
The fix for bug 924622 seems to have resolved several Android shutdown bugs, but not this one, intermittently affecting Android 2.2 jsreftest-3. $ ./intermittent_stats.py -d 7 1008422 OS's: 45 (58.4%): Android 2.2 Armv6 Tegra 31 (40.3%): Android 2.2 Tegra 1 (1.3%): Android 4.0 Panda Test Group: 68 (88.3%): jsreftest-3 6 (7.8%): jsreftest-2 2 (2.6%): jsreftest-1 1 (1.3%): plain-reftest-3 https://tbpl.mozilla.org/?tree=Try&rev=3d5269c7638b shows that the hang happens during NotifyObservers for NS_XPCOM_SHUTDOWN_OBSERVER_ID ("xpcom-shutdown"). But there are so many xpcom-shutdown observers, I'm not sure where to go from there. :nical -- Do you have any idea what might be happening here? Any advice for tracking this down further?
Flags: needinfo?(nical.bugzilla)
Depends on: 1020345
Lots of trial and error led to bug 1020345.
Flags: needinfo?(nical.bugzilla)
Inactive; closing (see bug 1180138).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.