Bug 1865931 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Some UI crashes/hangs are difficult to diagnose with external (tracing) profilers, as they do not capture gecko markers, and other firefox-specific information. In these cases, starting the Gecko profiler is not possible either, as it need a UI. 

This bug captures the process of correctly starting the Gecko profiler using a UNIX signal, but does not cover the process of stopping or gathering profiles (see bugs 1823370, 1865930, and TBD)
Some UI crashes/hangs are difficult to diagnose with external (tracing) profilers, as they do not capture gecko markers, and other firefox-specific information. In these cases, starting the Gecko profiler is not possible either, as it need a UI. 

This bug captures the process of correctly starting the Gecko profiler using a UNIX signal, but does not cover the process of stopping or gathering profiles (see bugs 1823370, 1865930, and 1865932)

Back to Bug 1865931 Comment 0