Open Bug 859990 Opened 7 years ago Updated 5 years ago

[meta] Tracking for mochitest "application timed out after 330 seconds with no output" in dom/plugins/test/

Categories

(Core :: Plug-ins, defect, P3)

All
macOS
defect

Tracking

()

People

(Reporter: gfritzsche, Unassigned)

References

Details

(Whiteboard: blocked by 525296)

We have a collection of mochitest timeouts which have in common:
* "application timed out after 330 seconds with no output"
* OS X
* no obvious failures in the logs

Currently we can't trigger breakpad on the hung application on OS X, bug 525296 will get us that.
Given that this is not limited to plugin tests, missing details and possibly many/most of them have a common cause we're currently waiting on bug 525296.

Filing this tracking bug so we can group them somehow and collect common info in one bug. Search used (and manually confirmed before adding as dependency):
https://bugzilla.mozilla.org/buglist.cgi?list_id=6243832&short_desc=application%20timed%20out%20after%20330%20seconds%20with%20no%20output&columnlist=op_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate&resolution=---&resolution=DUPLICATE&op_sys=Mac%20OS%20X&query_format=advanced&short_desc_type=casesubstring&component=Plug-ins&product=Core
Depends on: 622272
Priority: P2 → P3
Depends on: 866598
Depends on: 967512
Depends on: 956253
Depends on: 956247
Depends on: 952703
Depends on: 949973
Depends on: 945674
Depends on: 939710
Looking at the core::plug-ins component, a wide swath of plugin tests are still timing out randomly - including very simple tests that should not timeout short of a event loop lockup
The most recent ones added as dependencies don't have logs available anymore except bug 967512.
They are across Linux, Windows 7 and Mac OS X. For bug 967512 nothing stands out in the log.
I'd hope for seeing some hang stacks to at least get a vague idea of the issues.
See also: bug 1188052. I tried disabling the entire directory on OSX 10.6 and that led to a ton of other sadness.
You need to log in before you can comment on or make changes to this bug.