Closed Bug 1252683 Opened 9 years ago Closed 2 years ago

Intermittent browser_windowless_troubleshoot_crash.js | application timed out after 330 seconds with no output | application crashed [None]

Categories

(Toolkit :: General, defect, P3)

Product:
Toolkit
Component:
General
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: KWierso, Unassigned)

Details

(Keywords: intermittent-failure)

Luca, can you look into this, since you added this test? Thanks.
Flags: needinfo?(lgreco)
(In reply to Kris Maglione [:kmag] from comment #1) > Luca, can you look into this, since you added this test? > > Thanks. Looking at the failure logs, it seems that the issue can be related to "Troubleshoot.snapshot never call its callback" (which, looking into the |snapshot| method [1], seems possible, e.g. if one of the providers never calls the |providerDone| callback), in that case the promise will never be resolved and the tests will be stuck. I wonder if it would be better to move the "Troubleshoot.snapshot" part out from this case (e.g. by moving it in its own test file in the "toolkit/modules/tests/browser/", even if, obviously, move that part will not solve the issue, but it could make sense because the test case will be near to the implementation). [1]: https://dxr.mozilla.org/mozilla-central/source/toolkit/modules/Troubleshoot.jsm#153
That's probably a good idea, but it would be nice to figure out what's causing this, either way.
Component assigned to this issue changed to 'General', because the issue is actually originated by the |Troubleshoot.snapshot| method.
Component: WebExtensions → General
By looking into how the about:support information are collected by |Troubleshoot.snapshot|, the following data providers are the ones which have greater chances to generate the intermittents: - extensions - experiments - graphics I tried to force a failure in each of them but even if I'm able to get the test case to fail for timeout reasons, errors have been logged in the console, and in the above intermittent there were no logged errors, besides the timeout failure itself. The following seems the more recent change on "Troubleshoot.jsm" which has a chance of failing to resolve and block the Troubleshoot.snapshot function from calling its callback parameter: - https://hg.mozilla.org/mozilla-central/diff/4891238709e1/toolkit/modules/Troubleshoot.jsm (Bug 1212323: P3. Use promise with supportsHardwareH264Decoding.)
Clearing the needinfo flag, this intermittent is not happening anymore from a long time now.
Flags: needinfo?(lgreco)
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Severity: normal → S3

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

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