A 24MB profile is slow to analyse and takes 2.4GB RAM to open

[canova]

This issue is moved from https://bugzilla.mozilla.org/show_bug.cgi?id=1894447

Profile : https://share.firefox.dev/3JNDR49

Try going to the Marker Chart tab, or switch between different threads, or select a portion of the timeline and select it.

AR: The switching is slow . https://share.firefox.dev/3WtQx7Q / https://share.firefox.dev/4bmC6XH ER: Not so?

Feel free to INVLID if the perf is acceptable/expected (from what i understand, the pink-purple color indicates some settimeout() something in the profiled code, which forces the profiler to store additional data and make the profiles larger/slower to manipulate)

┆Issue is synchronized with this Jira Task

[mstange]

#5120 has another profile where getMarkerIndexToTimingRow is also the bottleneck.