306159 - When many tabs are open, and operation times out, can't close dialog (after hibernate)

Status: RESOLVED WORKSFORME

(Core :: Networking: HTTP, defect)

Description

[Brian 'netdragon' Bober]

I had 23 tabs open, and I clicked on a link, then switched to another tab, and
clicked a link, and continued to do so a couple more times, and was reading a
page, when one of the other tabs timed out. I got the dialog, "Operation timed
out, couldn't reach blah blah" or something like that. The problem is, when I
clicked "OK", it stayed open. I tried going into DOM inspector and get rid of
the object, but to no avail. Users are forced to kill the window.

Expected result: Clicking "OK" closes dialog.

Actual result: Clicking "OK" doesn't close dialog.

This could be a dataloss issue, as something in the tabs could be important, and
since dialogs are window-modal, you lose everything.

Comment 1

[Brian 'netdragon' Bober]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225
Firefox/1.0.1 (ax)

I found a "workaround": I deleted (in DOM inspector) the tab the dialog was
attached to, and then I could close the dialog by clicking "OK".

Comment 2

[Brian 'netdragon' Bober]

I just noticed, that after I got the dialog out, even though I could switch
tabs, I could close any tabs, only the entire window (except through DOM
Inspector). Maybe the reason the dialog wasn't responding was related to the
reason the tabs weren't responding.

Other useful information: I had hibernated with those 23 tabs in the window
prior to this happening.

See also: 
bug 304153  	doesn't survive hibernate

I was also seeing slow activity in tabs before this happened and after I removed
the dialog with DOM Inspector

Comment 3

[Brian 'netdragon' Bober]

I tried to reproduce this again, and although I couldn't get the dialog to stay
up with 18 tabs open this time, I did notice that at 18 tabs (some with Google,
some with Excite), the location box in the navigation toolbar started getting
periodically slow to handle keypresses, almost like Firefox was periodically
freezing up.

Comment 4

[Olivier Mengué]

This seems to be a duplicate of bug #304153.
They both depend on bug #265172.

Comment 5

[Wayne Mery (:wsmwk)]

Brian, 

is this 100% reproducible?  without tabs?  without hibernate?
what happens using FF2 or trunk?

Comment 6

[Wayne Mery (:wsmwk)]

Without more clear STR this bug seems to have little value, other than to document that dialog couldn't be closed on a network message that isn't 100% known.  Over to networking.  Note, no response from reporter, Brian, who wasn't able to recreate.  

I don't see how this is any more of a dataloss than any other hang, so changing dataloss>hang.  

Comment 7

[Kevin Brosnan]

No response - works for me