613998 - Wake Mac from sleep, browser goes 'offline' and force quit required (event loop spinning forever)

Status: RESOLVED DUPLICATE of bug 614958

(Firefox :: General, defect)

Description

[Simon Howes]

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b8pre) Gecko/20101121 Firefox/4.0b8pre
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b8pre) Gecko/20101121 Firefox/4.0b8pre

When waking Mac up from sleep, browser does not load any web pages, in fact there is zero net activity from the browser. Quitting the browser (cmd+q) or from menu bar causes app to hang, force quit is required (could be another bug).

Reproducible: Always

Comment 1

[Ed Lee :Mardak]

I've noticed this happening the last couple days. A wild guess is the TCP SYN change.. bug 592284?

Comment 2

[Ed Lee :Mardak]

Attachment: stuck offline

I sampled the process when Firefox wouldn't let me quit. But some reason I can't save the output. I've got just a screenshot of it for now.

Comment 3

[Ed Lee :Mardak]

20 ok? http://hg.mozilla.org/mozilla-central/rev/baa6cc2f72e4
21 bad http://hg.mozilla.org/mozilla-central/rev/be4b69a4babf

Build from 1121 definitely is bad, but because I don't have a deterministic STR, 20 seems good so far.

Doing File -> Work Offline can trigger this as well as it eventually calls SetOffline:

nsIOService::SetOffline(int)
 nsSocketTransportService::Shutdown()
  nsThread::Shutdown()
   NS_ProcessNextEvent_P(nsIThread*, int)
    nsThread::ProcessNextEvent(int, int*)
     nsEventQueue::GetEvent(int, nsIRunnable**)
      PR_Wait
       PR_WaitCondVar
        _pthread_cond_wait
         __semwait_signal

I don't know what exactly leads up to SetOffline spinning forever. A fresh restart doesn't trigger it, but after some browsing, it'll go bad when I select Work Offline.

Comment 4

[(no longer active)]

I think my patch in bug 614286 addresses this problem completely.

Comment 6

[(no longer active)]

So, the symptom in comment 0 is not exactly that of bug 614286 (the thing which happens after trying to quit is).

I'm not still convinced that this is the exact same issue as bug 614286, so I'll reopen this for now and will try to reproduce this once bug 614286 is fixed.