1310742 - profiling webswing for 10s causes firefox to become unresponsive (+3.5GB memory consumption)

Status: RESOLVED DUPLICATE of bug 1152441

(DevTools :: Performance Tools (Profiler/Timeline), defect)

Description

[Clemens Eisserer]

Attachment: profile.json.bz2

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161013141419

Steps to reproduce:

profiled webswing for 10s: https://youtu.be/0ORg7aRT0ys

This problem can be reproduced by simply uncompressing and loading the attached profile.json file in firefox.


Actual results:

after stoping profiling, firefox started to consume 3.5GB memory and it became completly unresponsive while consuming 100% CPU


Expected results:

the profile result should have been displayed, as it works without any problems in google chrome

Comment 1

[Greg Tatum [:gregtatum]]

I believe this particular issue is resolved with Bug 1152441. The profile that is uploaded has a large amount of markers, which causes them all to be rendered at once in the unfixed versions. It's not in Firefox 50 yet, but if you try it out in Nightly it should work. I'm also cross referencing this with Bug 1160330.

The performance is not 100% great yet, but that will require a larger re-architecture of the tool with workers.