1848907 - Capturing (post recording) a CSS OMTA demo takes a long time and uses a lot of memory

Status: RESOLVED INVALID

(Core :: Gecko Profiler, defect, P3)

Description

[Mayank Bansal]

Go to https://codepen.io/waldo/pen/jZRrVe
Enable profiler and select the "gfx" preset
Start the profiler recording.
Record for 10 seconds
Capture the profile (i.e. press ctrl+shift+2)

AR:

1. It takes a long time from when you press ctrl+shift+2 to the profiler GUI (i.e. https://profiler.firefox.com/xxxxxx ) screen to appear.
2. The profiler takes a lot of memory (1.5GB+) during the capturing phase and while the profiler GUI is open
3. The resulting profiles are usually huge in comparison to other JS/canvas focussed profiles which sometimes exceeds the upload limit of the profiler.

I tried to capture a profile of the profiler capturing a profile: https://share.firefox.dev/3DZnKh4

ER: better profiling experience.

Comment 1

[Mayank Bansal]

Attachment: memory-report.json.gz

Look at PID= 27056

Comment 2

[Mayank Bansal]

Attachment: about:support

Comment 3

[Julien Wajsberg [:julienw]]

Just as a random guess, you can try enabling the feature "No Marker Stacks" in about:profiling, and see if this improves your situation.

Comment 4

[Mayank Bansal]

(In reply to Julien Wajsberg [:julienw] from comment #3)

Just as a random guess, you can try enabling the feature "No Marker Stacks" in about:profiling, and see if this improves your situation.

Enabling "No Marker Stacks" in about:profiling did not help.
The capturing still took a long time, and the memory use was also high (2GB - 3GB).