1632909 - Never loading content process launched from profiler

Status: RESOLVED DUPLICATE of bug 1631323

(Core :: DOM: Content Processes, defect)

Description

[Asif Youssuff]

Saw another stuck content process, tried to grab a profile. Once I "captured" a profile, the tab that loads to collect and process the data never loaded.

Attached is a backtrace of that tab process.

Comment 1

[Asif Youssuff]

Attachment: backtrace from tab launched via firefox profiler

Comment 2

[Chris Peterson [:cpeterson]]

I believe this is a variation of the tab loading problems we're tracking in bug 1631323. I'll close this bug as a duplicate for now.

Attached file backtrace from tab launched via firefox profiler

By the way, I've been told that gdb backtraces are not useful for debugging Firefox hangs. Firefox can trigger signals that cause gdb to break into the debugger, even though Firefox would have gracefully handled the signal. So gdb backtraces often point to code that is not a problem.

Profiles captured using the Firefox Profiler extension are more helpful because they point to specific Firefox and Gecko (and JavaScript web content) code that is taking too much time or stopped running:

https://profiler.firefox.com/