1483433 - Memory profiling can lock up the content process

Status: NEW

(DevTools :: Memory, defect, P2)

Description

[Paul Bone [:pbone]]

STR:

Open a new tab, get devtools memory profiling ready.

Navigate to http://www.elegantreader.com/item/14804993 

While it's loading (you'll see a spinning "busy" thing) capture a memory snapshot.

Browse the snapshot for a little while, in less than 10 seconds the content process will become pinned at 100% CPU and Firefox won't respond to any input.

Expected result:

Sometimes things are going to be slow, but there should be something in the UI to show the user the progress, the main processes should not be locked up, I should be able to work with other tabs.  There should be some feedback to show me why it's being slow/processing, so I know which actions can cause this and which don't, and use them more carefully.

Comment 1

[Julien Wajsberg [:julienw]]

I don't reproduce for now.
Can you explain which view you were browsing, and also if you were capturing the stack traces ?

Thanks Paul !

Comment 2

[Paul Bone [:pbone]]

I tested again, I was able to reproduce it with Record call stacks on, in the 
aggregate report, for a memory snapshot of 27.85MB.  It hangs when I expand
the tree for JSScript which is the very first item in that report.

Then my laptop crashed completely while I was trying to capture a profile.  I'll try again.

Comment 3

[Julien Wajsberg [:julienw]]

I still don't reproduce :(

I tried capturing twice while loading: the first time the snapshot is 65MB, the second time it's 205MB. But in both cases I could work on the memory tool without an issue.