201970 - Sometimes I get a tab that I opened (usually from a middle-click) that won't close

Status: RESOLVED DUPLICATE of bug 137477

(SeaMonkey :: Tabbed Browser, defect)

Description

[Jason Pfeil]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319

I can't reproduce this reliably, but starting with version 1.3.0 and continuing
through 1.4a, I occasionally get a tab that I open (usually from a middle-click)
that won't respect the close command.  Either from the close widget, the context
menu of right-clicking on the tab, from the File->Close Tab menu, or from the
CTRL-W hotkey.  Eventually, I build up about 5 uncloseable tabs and have to
close the window.

Reproducible: Sometimes

Steps to Reproduce:
1.  Middle-click on a URL
2.  Try to close the tab through any of the UI-provided methods.
3.

Actual Results:  
This works about 80-95% of the time but sometimes the tab won't close.

Expected Results:  
Close the tab 100% of the time.

I was using the Classic theme.  The 1.3.x versions were compiled out of garnome,
but the 1.4a version was the RedHat 7.3 binary downloaded from the mozilla.org
page.  The version was the mozilla-i686-pc-linux-gnu-1.4a-sea.tar.gz downloaded
from:

http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4a/mozilla-i686-pc-linux-gnu-1.4a-sea.tar.gz

My md5sum:

f07cfc6fa79c575ef0a7f03172306565  tmp/mozilla-i686-pc-linux-gnu-1.4a-sea.tar.gz


Is there anything that I can do to help debug this?  Can I look at the
javascript console to see if there are any errors reported?

Thanks!

--Jason

Comment 1

[Jason Pfeil]

OK.  It happened again this morning and I opened the javascript window and saw
the errors appear as I clicked the close-button in the right hand side of the
tab bar.

The attached screenshot shows them.

Comment 2

[Jason Pfeil]

Attachment: Screenshot of javascript console showing errors.

Comment 3

[Hermann Schwab]

could be a dupe of bug 112337, have a look at bug 201947

Comment 4

[Jason Pfeil]

I took a peek and they are complaining about focus issues for the most part. 
This is not a focus issue as I cannot even close the tab by clicking on the
close-tab button.

I'll keep looking, though.

--Jason

Comment 5

[Jason Pfeil]

How ironic.  I can't close the tab that this bug report is in.  Yet, I can still
use hotkeys.  Is there a way to dump the contents of the javascript console to a
file for examination of it?  I can't select the text and cut-and-paste it...

Thanks!

--Jason

Comment 6

[Jason Pfeil]

I did just notice one thing...in this tab that I can't close, the spinner
doesn't do anything.  It does for the other tab that I can close, but not this one.

Just in case that helps.

--Jason

Comment 7

[Jason Pfeil]

This bug does appear to be different from the others you asked me to look at.

The first one, bug 112337, is describing only tab-switching hotkeys that don't
work.  However, in this case, the hotkeys *do* work.  The only one that doesn't
is CTRL-W, and that hotkey generates the same javascript errors that clicking on
the tab-close button does.

The second bug, bug 201947, only describes "gray" tabs.  Ones that are created
by attempting to middle-click on a bad link.  In this bug that I am reporting,
this happens on valid links and not bad links.

I hope this research helps you and thanks for a great product!  Mozilla is the
best (most correct with excellent speed) renderer out there, bar none.

--Jason

Comment 8

[Torben]

b.WebProgress has no properties = bug 137477

*** This bug has been marked as a duplicate of 137477 ***