Bugzilla

(In reply to Markus Stange [:mstange] from comment #5)
> Attachment 9370867 [details] shows the following:
> 
>  1. On the main thread, `ContentParent::KillHard` blocks in `ExceptionHandler::WriteMinidump`
>  2. On the "Breakpad ExceptionHandler" thread, `MinidumpGenerator::WriteBootargsStream` blocks in `malloc`
>  3. On the "com.apple.NSEventThread" thread, `malloc` is suspended in the kernel: `*11  ??? (kernel.release.t6020 + 734208) [0xfffffe0008613400] (suspended) 1-11`
> 
> Not sure what to make of this.

Is this the Apple profiler freezing the parent process to get the thread stack while the parent process was trying to write the minidump?

Am I right in thinking the KillHard stack is a result of the force quit? But we're interested in the original hang.

(In reply to Markus Stange [:mstange] from comment #5)
> Attachment 9370867 [details] shows the following:
> 
>  1. On the main thread, `ContentParent::KillHard` blocks in `ExceptionHandler::WriteMinidump`
>  2. On the "Breakpad ExceptionHandler" thread, `MinidumpGenerator::WriteBootargsStream` blocks in `malloc`
>  3. On the "com.apple.NSEventThread" thread, `malloc` is suspended in the kernel: `*11  ??? (kernel.release.t6020 + 734208) [0xfffffe0008613400] (suspended) 1-11`
> 
> Not sure what to make of this.

Is this the Apple profiler freezing the parent process to get the thread stacks while the parent process was trying to write the minidump?

Am I right in thinking the KillHard stack is a result of the force quit? But we're interested in the original hang.