Closed
Bug 1286366
Opened 9 years ago
Closed 1 year ago
As a user I want to provide more details when filing a hang bug
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
People
(Reporter: Harald, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [ele:1a])
The general theme is hangs, both finite & infinite, and the ability to provide additional details to enable investigation of the issue. Bug 1278794 is an example issue that can not be investigated further.
Possible solutions here is a specific about:hangs page or options on about:performance that provides exportable hang history.
| Reporter | ||
Updated•9 years ago
|
platform-rel: --- → +
| Reporter | ||
Comment 1•9 years ago
|
||
Could we track this as part of profiler work?
Flags: needinfo?(clarkbw)
Comment 2•9 years ago
|
||
Yes, can you create a meta bug to collect this? I believe there are others as well.
Flags: needinfo?(clarkbw) → needinfo?(hkirschner)
Updated•9 years ago
|
Whiteboard: [platform-rel-Facebook]
Updated•9 years ago
|
Rank: 35
Updated•8 years ago
|
platform-rel: + → -
Whiteboard: [platform-rel-Facebook]
| Reporter | ||
Updated•8 years ago
|
Whiteboard: [qf]
Updated•8 years ago
|
Whiteboard: [qf] → [qf:p5]
Updated•8 years ago
|
Whiteboard: [qf:p5] → [qf-]
Whiteboard: [qf-] → [qf-][ele:1a]
Updated•3 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-][ele:1a] → [ele:1a]
Updated•3 years ago
|
Severity: normal → S3
Closing due to all dependencies being closed and overall inactivity. Please reopen if this is not correct.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Updated•1 year ago
|
Component: General → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•