Closed
Bug 1156172
Opened 10 years ago
Closed 10 years ago
Need a list of crash (hang) reports in mozilla::MediaShutdownManager::Shutdown where other threads contain wasapi_stream_init
Categories
(Socorro :: Data request, task)
Socorro
Data request
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kinetik, Assigned: benjamin)
References
Details
Attachments
(1 file)
4.91 KB,
text/plain
|
Details |
In trying to debug bug 1135562, it's hard to guess the severity of the problem or look for any type of version/etc. correlation because there are many types of hangs caught under the same mozilla::MediaShutdownManager::Shutdown stack. I'd like a report that contains only those with mozilla::MediaShutdownManager::Shutdown in the hung (main thread) stack *and* has wasapi_stream_init on one of the other threads, please.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(chris.lonnen)
Assignee | ||
Comment 1•10 years ago
|
||
When making these kinds of requests, it would be useful to include a link to the base supersearch that needs refinement.
Do you care about the branch/version of Firefox?
Assignee | ||
Comment 2•10 years ago
|
||
http://bsmedberg.github.io/crash-stats-api-magic/analyze-crash.html?url=https%3A%2F%2Fcrash-stats.mozilla.com%2Fapi%2FSuperSearch%2F%3Fsignature%3D~mozilla%253A%253AMediaShutdownManager%253A%253AShutdown%26_columns%3Ddate%26_columns%3Dsignature%26_columns%3Dproduct%26_columns%3Dversion%26_columns%3Dbuild_id%26_columns%3Dplatform&rulecount=2&rule0_action=filter&rule0_fn=function%28d%29%20%7B%0A%20%20var%20ok%20%3D%20false%3B%0A%20%20d.json_dump.threads.forEach%28function%28thread%29%20%7B%0A%20%20%20%20thread.frames.forEach%28function%28frame%29%20%7B%0A%20%20%20%20%20%20if%20%28frame.function%29%20%7B%0A%20%20%20%20%20%20%20%20console.log%28%22frame.function%22%2C%20frame.function%29%3B%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20if%20%28frame.function%20%26%26%20frame.function.indexOf%28%22wasapi_stream_init%22%29%20!%3D%20-1%29%20%7B%0A%20%20%20%20%20%20%20%20ok%20%3D%20true%3B%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%29%3B%0A%20%20%7D%29%3B%0A%20%20return%20ok%3B%0A%7D&rule1_action=map&rule1_fn=function%28d%29%20%7B%0A%20%20return%20%5Bd.uuid%2C%20d.signature%5D%3B%0A%7D
(to use the tool, choose 'Fetch' and when that's ready 'Recalculate'
Of the first 100 crashes with that signature, 18 of them have wsapi_stream_init on the stack. I'll attach that list.
Assignee | ||
Comment 3•10 years ago
|
||
Assignee: nobody → benjamin
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•10 years ago
|
||
I'm going to call this FIXED. Let me know if you need anything different from this.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(chris.lonnen)
Resolution: --- → FIXED
Reporter | ||
Comment 5•10 years ago
|
||
Thanks Benjamin, that's great. I'll dig through those results, and it looks like your tool while be able to answer any further questions I might have.
You need to log in
before you can comment on or make changes to this bug.
Description
•