Seems to be empty for both call tree and flame view

I will look into this.

I see this in the logs, but I'm not sure if it is related or not: > Handler function threw an exception: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIWebProgress.DOMWindow]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js :: TabActor.prototype._docShellsToWindows/< :: line 1175" data: no] > Stack: TabActor.prototype._docShellsToWindows/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:1175:11 > TabActor.prototype._docShellsToWindows@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:1172:1 > TabActor.prototype._notifyDocShellsUpdate@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:1198:19 > TabActor.prototype._onDocShellCreated/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:1150:7 > makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:83:14 > Line: 1175, column: 0

I too was seeing that, but I always get console spam in BT, and not sure if this was occurring without allocations recording or not.

Also seeing some of this: > Handler function DebuggerTransport.prototype.onOutputStreamReady threw an exception: [Exception... "Component returned failure code: 0x80470007 (NS_BASE_STREAM_WOULD_BLOCK) [nsIOutputStream.write]" nsresult: "0x80470007 (NS_BASE_STREAM_WOULD_BLOCK)" location: "JS frame :: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/transport/packets.js :: JSONPacket.prototype.write :: line 197" data: no] > Stack: JSONPacket.prototype.write@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/transport/packets.js:197:17 > DebuggerTransport.prototype.onOutputStreamReady<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/transport/transport.js:276:7 > makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:83:14 > Line: 197, column: 0

(In reply to Nick Fitzgerald [:fitzgen][:nf] from comment #5) > Created attachment 8624354 [details] [diff] [review] > WIP debugging With this patch applied and then using the browser toolbox perf tool, I get these logs: > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites > console.log: FITZGEN: getAllocations > console.log: FITZGEN: allocations.length = 15 > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: emitting > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: done > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites > console.log: FITZGEN: getAllocations > console.log: FITZGEN: allocations.length = 12 > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: emitting > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: done > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites > console.log: FITZGEN: getAllocations > console.log: FITZGEN: allocations.length = 10 > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: emitting > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: done > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites > console.log: FITZGEN: getAllocations > console.log: FITZGEN: allocations.length = 5 > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: emitting > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: done > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites > console.log: FITZGEN: getAllocations > console.log: FITZGEN: allocations.length = 13 > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: emitting > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: done > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites > console.log: FITZGEN: getAllocations > console.log: FITZGEN: allocations.length = 8 > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: emitting > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: done > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites > console.log: FITZGEN: getAllocations > console.log: FITZGEN: allocations.length = 2 > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: emitting > console.log: FITZGEN: MemoryFrontFacade._pullAllocationSites: done So, the allocations log is working just fine. The actor is working just fine. The facade stuff seems to be working fine, and is emitting allocations events. This makes me believe it is a frontend bug.

(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #3) > I too was seeing that, but I always get console spam in BT, and not sure if > this was occurring without allocations recording or not. I think both are unrelated.

This is the same bug as bug 1177558. Once allocations work in normal content again, this fixes this issue. Still dep on bug 1172180