Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Firefox/17.0 ID:20120923042010 When I was updating Aurora from 120919 to 120923 I triggered the restart of the browser via the about window. Firefox didn't shutdown but keeps running with about 35 threads and a memory usage of 700MB. This was ongoing for a couple of minutes. After recording some information I finally had to force kill the application. I haven't had such a situation for a long time. So far I haven't tried to reproduce but will do once the updates of today are available.

If necessary I have an aurora trace via Instruments available. If wanted I can share it via e.g. dropbox. It's about 190MB in size. For now here the Aurora report information.

In the activity monitor sameple HTTP is waiting on ... something. The SSL code is also waiting on ... something. Possible deadlock there?

So here the link to the instrument trace: https://www.dropbox.com/s/7s5f6z289ltwb9c/aurora.trace.zip

I have Aurora 17.0.2 hung with pretty much the same call graph as :whimboo's activity monitor sample https://bug793637.bugzilla.mozilla.org/attachment.cgi?id=663992 I'll try to get symbols and attach a debugger...

Irving, do you see the same in 18.0 or even 16.0 beta? The latter could possibly be a blocker.

I've only been running Aurora, and I don't have steps to reproduce. Unfortunately when I tried to attach a debugger the hung process exited, so I don't have any more evidence except a saved Activity Monitor sample.

I have updated from yesterdays to todays build without a hang involved now. It could be related to a hibernation which I haven't done during today. I will keep an eye on it.

Tracking for now, and sending over to Ehsan to take a look at the sample when he gets the chance. I suspect that if this happens around updates, bgupdates may be implicated.

This has every indication of being a deadlock. I don't see any evidence to believe that this has anything to do with bgupdates.

Thanks Ehsan. Josh - can you recommend somebody to take a look at this on the networking side?

Patrick, Brian, Honza - any idea what is going on here?

Known deadlocks: bug 698882, bug 729536, bug 726103.

no need to track, duplicate of a bug that's been around since 13.