Closed Bug 1182324 Opened 10 years ago Closed 10 years ago

Paired minidumps triggered from plugin hang ui should capture main thread, not plugin hang ui thread

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: bugzilla, Assigned: bugzilla)

Details

It's not useful to examine a minidump that contains the plugin hang ui on the call stack; what we really want is whatever was going on with the main thread.
I don't understand what this bug report is about. Crash reports capture a minidump, which contains all the threads. Is this about which thread we display by default on crash-stats?
Flags: needinfo?(aklotz)
More importantly, which thread we display by default when viewing a multi dump. Is that metadata that we can include at the time of dump generation, or is this a change that needs to be done in the multi-dump tool?
Flags: needinfo?(aklotz) → needinfo?(benjamin)
We might be able to annotate additional thread IDs in the client, but it doesn't really sound worth it. If we can make this change just in the client that would be better. I just auto-expand thread 1, but I could not auto-expand any thread if that would be clearer.
Flags: needinfo?(benjamin)
No big deal. PEBKAC.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.