Bug 1979124 Comment 24 Edit History

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

Perfect!

Dana, the Socket thread is deadlocking with a BgIOThreadPool thread, which is doing a blocking call of the form `futures_executor::block_on(moz_task::spawn_onto("find_objects", &self.thread, ...))` during a callback from NSS for find_objects.
Perfect!

Dana, the NSS session lock is being held by a BgIOThreadPool thread during a `find_objects` callback from NSS. That thread is trying to run the `find_objects` work synchronously on the `osclientcert` thread, but the `osclientcert` thread is also trying to synchronously drop a `ThreadSpecificHandles` on the cert key's thread. I'm not sure which thread that is - maybe the `osclientcert` thread is deadlocking with itself? Or it might be deadlocking with one of the other two threads.
Perfect!

Dana, the NSS session lock is being held by a BgIOThreadPool thread during a `find_objects` callback from NSS. That thread is trying to run the `find_objects` work synchronously on the `osclientcert` thread, but the `osclientcert` thread is also trying to synchronously drop a `ThreadSpecificHandles` on the identity key's thread. I'm not sure which thread that is - maybe the `osclientcert` thread is deadlocking with itself? Or it might be deadlocking with one of the other two threads.

Back to Bug 1979124 Comment 24