Closed
Bug 1159089
Opened 10 years ago
Closed 9 years ago
CRASH: Performance tool crashes with nsIMessageSender.sendAsyncMessage with memory enabled
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect, P1)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jsantell, Unassigned)
References
Details
(Whiteboard: [polish-backlog])
I've gotten this a few times -- pulled down anew and rebuilt and still came across this. Seems to happen irregularly, but running an octane test generally causes it to occur immediately. Only seems to occur with memory enabled.
Occurs in both e10s and non e10s.
Handler function threw an exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMessageSender.sendAsyncMessage]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js :: DebuggerServer.connectToChild/destroy< :: line 900" data: no]
Stack: DebuggerServer.connectToChild/destroy<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js:900:9
makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:82:14
DebuggerServer.connectToChild/onMessageManagerClose@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js:936:9
Reporter | ||
Updated•10 years ago
|
Comment 1•10 years ago
|
||
Is this a crash or an error in the console? If it is a crash, do you have the stack from about:crashes, or can you repro with a debug build + debuggger?
Reporter | ||
Comment 2•10 years ago
|
||
Crash: https://crash-stats.mozilla.com/report/index/0df0bdd5-9789-4251-8fb5-531822150428
This is a full crash, exiting in non-e10s, and crashing all tabs in e10s.
Reporter | ||
Updated•10 years ago
|
Blocks: perf-allocations
Reporter | ||
Updated•10 years ago
|
No longer blocks: perf-tool-v2
Comment 3•9 years ago
|
||
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #2)
> Crash:
> https://crash-stats.mozilla.com/report/index/0df0bdd5-9789-4251-8fb5-
> 531822150428
>
> This is a full crash, exiting in non-e10s, and crashing all tabs in e10s.
Any chance you could reproduce this with a debug build?
Does this happen with just allocations and not memory turned on? (Maybe we can stop blocking perf-allocations?)
Reporter | ||
Comment 4•9 years ago
|
||
Haven't seen this in awhile, but I've also had memory and allocations off. With them separate, I'll try allocations always on to see if old or new issues shake up
Updated•9 years ago
|
Whiteboard: [devedition-40] → [polish-backlog]
Reporter | ||
Comment 5•9 years ago
|
||
Haven't seen this.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•