Closed Bug 137477 Opened 23 years ago Closed 15 years ago

Some tabs cannot be closed

Categories

(SeaMonkey :: Tabbed Browser, defect)

Product:
SeaMonkey
Component:
Tabbed Browser
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: atmjav, Unassigned)

References

Details

(Whiteboard: [Hixie-P0])

Attachments

(4 files)

Unclosable tab screenshot
14.47 KB, image/png
Details
URL not refreshed correctly in jinxed tab when going to another page in session history
143.01 KB, image/jpeg
Details
Window title not properly refreshed when going from good tab to a jinxed tab
64.85 KB, image/jpeg
Details
This is a screenshot from Firefox 3 in the case when there is no close icon for the tab
6.03 KB, image/jpeg
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9+) Gecko/20020408 BuildID: 2002040803 I cannot close some of the tabs, unless by closing the whole window. This bug appeared a few builds before. Reproducible: Sometimes
similar: bug 131188. How are you trying to close the tab? Middle-button clicking, using the X, or right-click and choose "Close Tab"? Do all or only some of these fail? I haven't noticed this bug. (Usually closing by middle-clicking.) 2002041408, XP.
WFM I always close witth right-cliick + "close tab" an never hat this Problem in any built (actually: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:0.9.9+) Gecko/20020411)
[Mozilla 20020424?? (1.0 branch); Windows 2000] I've had this once, with a single tabbed window. I'm not sure if it was with the 2nd tab opened (bug 131188) or not (more likely I already had a couple open already). I couldn't close the particular tab window by right clicking and choosing 'Close Tab' or using the 'x'
I have the same problem sometimes, though it is not always reproducable. I have tried closing the tab by middle-clicking, clicking the "X", and also by right clicking and choosing "Close Tab." Nothing works.
I frequently see the behavior that CTRL-W does not work to close a specific tab, but clicking on the 'x' does work. This can be reproduced by: 1. clicking on this link: http://members.fortunecity.com/skuchin/otlv4_h.zip with CTRL pressed down in order to open it in a new tab. 2. A new tab opens but displays nothing, because a download starts. 3. Press "Cancel" on the download screen. 4. Switch to the new tab that has "(untitled)" as title 5. try to close it with CTRL-W WinNT 4.0 SP6a Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0rc2) Gecko/20020510
hmm, while further testing this, I detected that the Window can be closed by CTRL-W after clicking into the empty Window. Therefore my thing seems to be focus-related...
Reply to #6 CFM your results with Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc2) Gecko/20020510 It is more or less a keybord-shorrtcut problem or similar Owner / Reporte, please add Keyword "Keyboard Navigation" (or similar)
I am running 2002061104 and I currently have a tab that I cannot close. I a 9 tabs open atm, and it is the 7th tab from the left that I cannot close. The tab is a page that could not load - so it contains the address in the tab title (www.acm.wwu.edu/~schmoli/eclipse/) and when selected about:blank is in the location bar. Things I have tried to close it: - right clicking on tab title->close tab - select tab - file->close tab - select tab - click on X - select tab - CTRL-W Nothing will close it. I don't know if this is important or not, but I did previously select the tab and hit the reload/refresh button to try and get the page to load. Didn't work.
comment to #8 WFM with Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530 I can close tabs with - /file/closetab - right mouseclick / "close tab" - ctrl-w - click on closetab- button and even problem #6 #7 no WFM I think, there is something curious with your system and - please, tell us your complete mozilla system from "help" (as I did) - http://www.acm.wwu.edu/~schmoli/eclipse/ contains some HTML, but it is not a HTML- page ;-)
Depends on: 131188
Reply to #9 Sorry about the lack of information, this should be of assistance. Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1a) Gecko/20020611 If it helps I loaded the tab in the background via a middleclick. I tried to replicate it then, but I failed to do so.
For what it's worth, I've seen this on the trunk just now. For me it was the first tab that couldn't be closed. I didn't try the keyboard to close it, but the "x" certainly didn't work. That particular page was opened from a link in mail/news, and the URL was http://www.ctv.es/cartagena/ I cannot consistenly reproduce the bug, but I'll keep trying :-) Seen in: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a) Gecko/20020609 Changing OS to ALL since this does not appear to be windows related. Confirming the bug, at least 3 different people have seen this, and the bug meets the QA criteria. Also, bug 131188 is most likely a dupe of this one (or the other way around.) There's actually a procudure for reproducing this over there, but it doesn't do it for me.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
Please open the JS console and look for errors like this: Error: b.webProgress has no properties Source File: chrome://navigator/content/bindings/tabbrowser.xml#tabbrowser.addTab() Line: ?? Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://navigator/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line ??" data: no] and make sure to confirm them here! /HJ
I currently have a tab that cannot be closed, not via CTRL-W, not via the little "x" and also not by right-clicking the tab in the tab-list and selecting "Close Tab". In the Javascript-Console I get the following error every time I try to close the tab: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 30" data: no] I will have Mozilla open as long as my Computer does not crash, so if I should perform additional actions on the tab, please let me know. I hope this helps. Win 2k SP2 Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
*** Bug 157433 has been marked as a duplicate of this bug. ***
I think I'm seeing the same problem as pbclarke@alphalink.com.au (in Additional Comment #8). I'm using Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1b) Gecko/20020721; this is Windows 98 first edition on a Toshiba laptop where I've been using various Mozilla versions for months; it's the first time I've had this problem. I often have a single window open with multiple tabs from www.nytimes.com. I have a dialup connection which ties up my phone line, so I tend to open the home page www.nytimes.com, right-click on the link to each story I want to read, and choose "Open in New Tab". I often have several different tabs loading simultaneously. When all tabs have loaded, I disconnect from my ISP. This morning, my dialup connection failed while several of the pages were loading. I reconnected to my ISP, then clicked on each tab that hadn't finished loading and pressed Ctrl-r or clicked the Reload button. On one particular tab -- the one that later wouldn't close -- I accidentally did "Reload" *twice*, within one or two seconds of each other. (Maybe that double reload is what caused the problem?) After that, I ended up with a tab titled http://www.nytimes.com/2002/07/28/international/middleeast/28KURD.html (I can only see the first part of that title -- http://www.nytimes.com/20 -- in the tab; I can see all of the title by hovering the mouse pointer over the tab itself, and a yellow tool tip appears with the full title). The funny thing here is that the URL in that title is *not* the same as the URL of the page that I was trying to load in that tab! Instead, it's the URL of the page in *another* tab: the tab at the right-hand side of the four tabs in that window. When I click on the uncloseable tab, the URL in the location field changes to "about:blank" and I see a blank white window. (Sorry, I don't know the exact Mozilla name for the "location field"; it's the wide and short white area between the Stop and Search buttons.) I tried three times to close that tab -- with the "x" at the right end of the tabs, with Ctrl-w, and by choosing "Close tab" from the top "File" menu. Nothing worked. When I later opened the Javascript console, I saw three consecutive errors like the following: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 31" data: no] All three errors seemed to be identical, so I've only shown one here. (There were some other errors and warnings, too, that seemed to be about other things.) I'll put my laptop into Standby mode so that -- with luck -- it won't freeze and lock up like it usually eventually does :-(. If you want me to do any more tests before the battery dies, please email me (jpeek@jpeek.com) ASAP!
Intermittently seeing the same problem. Confirming javascript errors as requested by comment 12 - one for creating the empty tab (which can load pages and follow links, but doesn't update the location bar (until you've focussed another tab) or activate the throbber), one for trying to close it. (Either with ctrl-w, middle-click, contextmenu close tab or the X.) Error: b.webProgress has no properties Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.addTab() Line: 42 Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 31" data: no]
This screenshot (attached) shows an example of a tab that cannot be closed. As you can see, the document has a URL which exists (a BBC article), but the page is empty and the address box says "about:blank", even though the status bar says "Document: Done".
Elaborating on my immediately preceeding comment, I currently have the same bug as described in #8 and #15. The URL is http://news.bbc.co.uk/2/hi/sci/tech/2175837.stm, which has failed to display (a bug in itself, but I don't know whether _that_ is Mozilla's bug or the BBC's, or what). I don't know exactly why it failed to display, but I have only 40Kbps connection, and I'm in the middle of a large download (Getright, not Mozilla) which is using most of that bandwidth. Like #8, I refreshed (but with F5) before trying to close it. It won't close with Ctrl-W, clicking X, or right-clicking > "Close tab". I'm using Mozilla 1.1b (2002072104) on Windows 2000.
*** Bug 163470 has been marked as a duplicate of this bug. ***
I'm using build 2002081904, Win2k Sp-3, open the tab by ctrl+click from bugzilla main page and target page never display. Tab look fully functional, I'm browsing several sites without problem but actually can not close the tab (try with ctrl+w, r-click "close tab", "x" button, file|close tab).
steps to reproduced: 1.open Mozilla browser 2.type in location bar: http://www.google.com.br/ 3.create new tab 4.type in location bar: http://www.google.com.br/ again 5.right-click and choose "Close Tab" 6.the tab is closed 7.open new tab again 8.is showing 3 tabs (should be 2 only) 9.close tabs do not work more
sorry, win98, Mozilla 1.1 beta, build 2002082109
I have this bug under Windows XP with Mozilla 1.1 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 I noticed the following error message, which I got for every tab I closed, that was located in the tab bar before the bugged Tab. This could be related to this problem. ============ Error: listener has no properties Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.updateCurrentBrowser() Line: 25 ============
Mozilla 1.1 Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.1) Gecko/20020826 Same happens here when I try to open a new tab with middleclick and for some reason the URL won't load. JS console: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 31" data: no]
QA Contact: sairuh → pmac
compare bug 140859
Whiteboard: [Hixie-P0]
wfm on windows 2K (netscape branch build: 2002-11-07-08-1.0)
Please not that WFM does not apply here. IMO this is an intermittent bug that shows up after running Mozilla for some period of time or some activity or website the browser has experienced during operation.
I would agree with that. I've seen it on Mozilla 1.2 beta. Will test it with a later build.
*** Bug 140859 has been marked as a duplicate of this bug. ***
No longer depends on: 131188
*** Bug 131188 has been marked as a duplicate of this bug. ***
All/all on basis of last dupe.
Hardware: PC → All
Summary: Some of the tabs cannot be closed → Some tabs cannot be closed
I am doing some testing today too. Will run the browser for a long time (24 hours or so at least) and see if this recent build runs into the problem (or crashes first). Usually it had been causing the problem sooner than that time period.
So far I am not seeing the tab closing problem or any other tab flakiness that I'd been seeing for many weeks. It is truly an ugly problem, so let's hope it just disappeared!
I would like to say that this bug has not just disappeared. I experienced this problem of not being able to close a tab for the first time that I remember back on 1.2 beta and now I am seeing it again on 1.2 final. I am using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126. Like the others above, I am unable to close the tab using any and all of the methods. I am also getting the same type of message in the JavaScript console which is pasted below. I have not been able to consistently reproduce the bug however. It should be noted it occurred after my having first seen the behavior where pressing Ctrl-T opens two tabs instead of one. Someone else mentioned that above. Can we please not ignore this bug, it most definitely hasn't resolved itself. Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no]
Flags: blocking1.3a?
I also see this in 1.2.1
The question right now is, do we see this bug anymore in 1.3a builds? I am not seeing the problem just yet.
Flags: blocking1.3a? → blocking1.3a-
Re comment #36 : Yes it is. I just have such an unclosable tab here (using 2002120408) and get the same JS error message as Armen two comments above. The URL works now (new tabs with it can be closed), URLbar says 'about:blank, while tab is labeled with the URL (http://cvs.sslug.dk/cvs2html).
Mozilla 1.2.1 Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2.1) Gecko/20021130 Windows ME, 256Mb RAM I get this as well. The tab doesn't load, but stays blank. All other act as per usual. I can't close the tab by switching to it and using CTRL+W or CTRL+F4, or right-clicking and selecting "close", or switching to it and clicking the X at the far right. "Reload Tab" does nothing. Closing the browser window is as usual. I usually seem to get this when using "Open Link in new Tab" rather than opening a blank tab and pasting a url. It doesn't happen very often. The url always stays at "about:blank", though the tab title still has the URL clicked on it. I remember seeing five or six "uncaught exception" errors in the javascript console. Due to it's apparently random nature, I would guess at something to do with memory management; Windows ME is particularly bad at this :| "...intermittent bug that shows up after running Mozilla for some period of time..." Has anyone witnessed this bug on linux?
Okay, I just had it happen again. Probably going to have to reboot soon :p I closed all tabs except the "stuck" one, and then sucessfully closed it with CTRL+W. The javascript console has 4 of these: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no] plus some sidebar stuff which is probably nothing to do with this.
It's interesting, I'm surprised this bug is around anymore since I saw it so regularly before and haven't seen it in a couple weeks or so of testing. I talked with the developer of Tabbrowser Extensions and we agreed that he had a problem with a few versions of it that also caused an identical tab closing problem, but once he stated it was fixed, I didn't have any further problems (after I reinstalled the fixed one). I'm not sure whether there were two separate issues going on to cause this problem or not. Anyway, I would suggest that people who are using this extension try a newer one.
Problem still exists in 1.3a. It seems that it happens more frequently on slow net connections, and therefore probably has to do with opening new tabs while some others are loading.
I see this javascript error in 1.3a: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no] In addition of this one, but that is perhaps another bug: Error: inspector is not defined Source File: chrome://inspector/content/sidebar.js Line: 125
Windows XP Professional Version 2002 SP1 Mozilla 1.3a Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212 visited http://phish.marko.net/coverart clicked the image linked to extreme-dm.com clicked the "Summary" link clicked the "Referrer Tracking 1" link tried to close the tab, but couldn't tried closing by: right-clicking on tab and selecting "Close Tab" clicking on the "X" icon on far right of tab toolbar clicking File>Close Tab pressing Ctrl+W The following errors in JavaScript Console are related to this bug: This error comes up when trying to close the tab via any of the aforementioned methods: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no] This error comes up when attempting to move to the tab from another tab via keyboard shortcut, either Ctrl+Page Up or Ctrl+Page Down (the error does not appear when moving from the jinxed tab to a tab that is OK): Error: listener has no properties Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.updateCurrentBrowser() Line: 22 if I can be of more help, please let me know! :)
2 additional odd things I noticed about the jinxed tab: 1) when navigating to another page in session history, via down arrow next to the forward or back button, the URL of the page navigated to doesn't refresh properly, i.e. the URL of the page you come from is still in the address bar, even though you're looking at another page. The correct URL is not displayed until you click onto another tab and then click back onto the jinxed tab. :\ I will submit a screenshot of this behavior... 2) when clicking onto the jinxed tab from a good tab, the window's old title (actually the title from the last tab viewed before viewing the jinxed tab) remains instead of refreshing with the title of the page viewed in the jinxed tab. the second screenshot will show this behavior notice that in both screenshots, the title as displayed in the tab itself is "(Untitled)" :\
This is a screenshot of odd behavior #1 in c44. It shows how the URL did not refresh to show the currently viewed page's URL, when navigated to via the session arrow next to the back/forward buttons inside a jinxed tab. Notice that the window's title *does* change correctly, though...
Screenshot of behavior #2 in comment 44. Notice the window's title is still "Bug 137477..." instead of the title of the page displayed. This happens when clicking from one good tab to one jinxed tab...
Re comment #43: I can still close the tab with 2002121608 on Win2k. Is there something more specific like loading a tab in the background or so? Can you reproduce it 100% with the given steps? (Try to read and follow them as if you had not written them yourself to find where I might have done something wrong)
I has always opened the tabs in background when I see the problem.
Still not reproducable that way.
I've encountered this problem several times too (1.2.1/Windows). What's interesting (and annoying) is that after closing the window containing the unclosable tab and then restarting the browser, Mozilla will sort of "hang" at the splash screen stage while causing the hard disk to be heavily accessed (virtual memory?). I suggest raising the severity to 'major'. Also, bug 181546 seems to be a duplicate of this bug.
Andreas, I cannot reproduce this bug easily. I had started the tab that became jinxed by pressing Ctrl+T, I believe, but haven't reprod this since my bug report. :(
Also happening on Linux now. Bug has been present for some releases. Current release: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9 Experiencing the same symptoms. It happens rarely. Unable to reproduce. Always opening tabs in background with middle click. Problematic tab can't be closed by any method. Javascript console dump (some repeated messages skipped): Error: can't decode principals (failure code 80040154) Error: b.webProgress has no properties Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.addTab() Line: 45 Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no] Error: listener has no properties Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.onLinkAdded() Line: 36 Error: element has no properties Source File: chrome://cookie/content/cookieNavigatorOverlay.xul Line: 128 Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no] Error: element has no properties Source File: chrome://cookie/content/cookieNavigatorOverlay.xul Line: 128
Windows XP Professional Version 2002 SP1 Mozilla 1.3a Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212 saw this again...it happened on a tab opened in the background w/ Ctrl+T. The following errors come up in the JavaScript Console: This error appears when switching to the jinxed tab w/ a keyboard shortcut (i.e. Ctrl+Tab, Ctrl+Page UP or Ctrl+Page Down) but NOT if switching w/ the mouse: Error: listener has no properties Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.updateCurrentBrowser() Line: 22 This error appears when trying to close the jinxed tab, either w/ a keyboard shortucut or w/ the mouse: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no] This error appears when I use the Back/Forward buttons, either left or right clicking on them (see the comments about the bizarre behavior in bug 126826, comments 121, 122, 123, 124 & 126): Error: listener has no properties Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.onLinkAdded() Line: 36 Btw, I *always* load tabs in the bg...not sure if that has any relevance to these bugs...
after closing all other tabs, leaving only the jinxed tab behind, I could not close Mozilla w/ Ctrl+W or by going to File>Close. However, when closing Mozilla by clicking the X icon @ the top right, I received this error in the JavaScript Console: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: <unknown filename> :: onxbldestructor :: line 3" data: no] Notice that this is different than the other "uncaught exception" I've seen while trying to close a jinxed tab, but not Mozilla as a whole. Maybe this can shed a bit more light on the subject....
I get the same error in Phoenix, except "/bindings/" is "/widgets/"... I suppose just due to movement of files in the packages. Gecko/20030112 Phoenix/0.5 Happens rarely, but very confusing when it does, and requires a restart.
*** Bug 189647 has been marked as a duplicate of this bug. ***
I see this bug on Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3a) Gecko/20021210, too. I have only seen this once on 1.2.1 and never on previous builds. On 1.3a I have seen this three times in two days. Javascript console says this: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no] The tab appeared when surfing on Yahoo groups. I load tabs in the background. One link, although correct (and I have highspeed Internet) did not load, but went to about:blank. I cannot close it with any method. There is one thing I can add to the findings reported here by the others. On the tab that I cannot close, I can load any web page normally. Just by clicking one of my bookmarks. Loads perfectly. But still it will not close, giving me the above mentioned Javascript error again - even on pages that do not contain JS.
Confirm uncloseable tabs in 1.3a Linux with XFT (it's got worse since upgrading from 1.2.1). Also confirm comment 44 part 2 (title not updated to jinxed tabs title). Reload button also fails to reload the tab. Tab not closed by clicking "Close other tabs" in a new tab.
I see this too. The unclosable tab was opened by middle-clicking a link to Google but for some reason it didn't load the content.
*** Bug 190325 has been marked as a duplicate of this bug. ***
I've seen this jinxed tab today and after closing Mozilla I've noticed that it's next start lasted much longer than usual. I've tried to strace it's busy thread while it was starting but all I got was: | munmap(0x4c368000, 167776256) = 0 | write(4, "\372", 1) = 1 | gettimeofday({1044557461, 911242}, NULL) = 0 | ioctl(5, FIONREAD, [0]) = 0 | poll([{fd=5, events=POLLIN}, {fd=30, events=POLLIN}, | {fd=3, events=POLLIN, revents=POLLIN}], 3, 0) = 1 | gettimeofday({1044557462, 170301}, NULL) = 0 | gettimeofday({1044557462, 339521}, NULL) = 0 | sched_get_priority_max(0) = 0 | sched_get_priority_min(0) = 0 | rt_sigprocmask(SIG_SETMASK, NULL, [RT_0], 8) = 0 | write(9, "\240\300 @\0\0\0\0\214\356\377\277\334E\36@\0\325%\10\0"..., | 148) = 148 | rt_sigprocmask(SIG_SETMASK, NULL, [RT_0], 8) = 0 | rt_sigsuspend([] <unfinished ...> | --- SIGRT_0 (Real-time signal 0) --- It took approx. 2.5 min. for Mozilla to start. Usually Mozilla starts in less than 10 seconds on my system (Linux 2.4.20, Celeron 466MHz, 192MB RAM, Mozilla 1.2.1).
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5 Win 2000 SP3. I've been running Phoenix for about 15 hours now, and I have 8 tabs open. The first thing I opened with that tab was CVS.com. Played around there a bit, put something in my shopping cart, etc. After that the tab was unclosable but still usable. The Current title of the Phoenix Window is "UPS Quick Cost Calculator - Phoenix" -- probably because that was the last tab I was viewing before this one. The title of this tab is "(Untitled)" and doesn't change. I don't believe that this bug has anything to do with how long Phoenix has been running. I can still close all the other tabs EXCEPT the one I'm using at the moment to submit this bug. The "X", CTRL-W and the "Close Tab" menu does not close it. I have not experienced this before this week, and I have seen it twice this week. I will try to reproduce it.
Mozilla 1.3b, Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210, Windows 2000 After a fresh install of 1.3b, this quickly surfaced. I saw exactly the same conditions/results in JS Console as reported in comment 43. The following appeared in the JS Console when I typed about:config and hit enter: Error: gHistoryStatus has no properties Source File: chrome://communicator/content/history/history.js Line: 158 If a dev wants a zip file containing the entire contents of the profile as this jinxed tab existed, let me know. :)
I forgot to mention that the steps that lead to the jinxed tab: I went to http://bugzilla.mozilla.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=GRE&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0= right-clicked on several dependency bugs (loading them into background tabs). One of the links didn't open and was labeled "Untitled". This was the jinxed tab. I may have "unjinxed" it by focusing on a non-jinxed tab, then focusing on the JS Console, then focusing directly on the jinxed tab...all w/ the mouse...as the entire tabbed window (containing around 7 tabs) closed after this when I clicked File>Close Tab, whereas previously Ctrl+W didn't work on that tab. I guess I could zip up the profile directory now that it's closed to see if there's a difference btwn that one and the one I zipped while the jinxed tab existed. Let me know if I should email these to someone.
Could this be related to bug 90337?
*** Bug 167749 has been marked as a duplicate of this bug. ***
Ere: this is a separate bug from bug 90337. This deals w/ a tab not closing, 90337 deals with an unresponsive URL bar.
Flags: blocking1.4a?
Keywords: nsbeta1
Earthsound, I am aware of that. The cause of different symptoms can be same though, and these both bugs exhibit similar behavior.
Ere, I see nothing similar between this bug and bug 90337, however I have been wrong before. ;) Btw, I still have the zipped profiles to offer as I mentioned in comment 63 and comment 64. :)
Just like to confirm that i've experienced this for the first time on Mandrake Linux (x86) with mozilla 1.3b. Tried clicking 'x', right-click/close and a mouse gesture as well. nothing! Not URL specific since the same URL was open in the next tab. P.S how does one attach a screenshot? would it be useful?
> screenshot? would it be useful? I don't think so. What would be really useful is a reliable way for everyone for reproduce this bug 100% (not just on some machines or occasionally). The lack of that is probably the reason why this bug still exists - without reliable reproduction, developers have a very hard time in general.
>What would be really useful is a reliable way for everyone for >reproduce this bug 100% (not just on some machines or occasionally). Well, I see it every time I browse a news site for approx. 10 minutes. What to do to reproduce it: -it helps to have a slow internet connection -open many links at the same time using type ahead and ctrl-enter, typically browse through news headlines and open every news in a new tab -it seems to help to open the new tabs while some other are loading (increased chance for this with slow internet connection)
I don't use TAF & ctrl-enter to open links, but instead middle-click them. But I do second that it seems to happen when you open a bunch of new tabs quickly. I often middle click 2-3 links before the first new tab has even appeared. (there are some annoying focus issues here, too)
That's not what I meant with "100%" "reliable". I mean do 1, do 2, do 3, etc. adn everytime you do that, the bug appear, on every computer, assuming the syteps are followed. I know this is hard to find with this bug (it's probably something time-based, 2 things have to happen to occur at the same time), I see the bug myself and havn't found a reproduction either, but it's really of key importance for fixing the bug.
Nav triage team: nsbeta1-
Keywords: nsbeta1 → nsbeta1-
I'm confirming this for Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3b) Gecko/20030308 I'm getting this JavaScript error Error: uncaught exception: [Exception... "Component returned failure code: 0x80 and I also got this error Error: can't encode principals (failure code 80004005) I don't know if this has been mentioned ( I've only skimmed the many posts), but the favicon (and the rotating arrows that signify loading) is also broken for the broken tabs. All in all the tab label seems to be broken in strange ways. I had 2 broken tabs at the same time today. One of them showed the URL of the last page before it broke (the URL, *not* the window title as it should have) which was http://slashdot.org btw. The other showed "Untitled". Both had no favicon. BTW, in all cases I remember only the tabs at the far ends broke. Usually the left-most tab seems to be first. But of course that could just be coincidence because I usually start with the left-most tab (or rather no tabs at all) and then middle-click on links in that window. Is there a way to set a Venkman breakpoint at the code that throws the exception?
Sorry, copy'n'paste error. The JavaScript message I get is longer of course. It's exactly the same as that in comment 57.
This bug seems to happen MUCH more often with 20030308 than with 20021202. I used to hit this bug only once every few days and never with multiple tabs but now it's become a real pain. Today alone I had about 10 broken tabs. Just a few minutes ago, 3 new tabs I opened were broken. The 4th worked again, though. I noticed that broken tabs that are opened with Ctrl-T have an "Untitled" label whereas broken tabs opened with middle-click have a URL as label. It might be useful to check how the tab code has changed from 20021202 to 20030308. Some change must have made this bug more pronounced. I also hit some other strange tab behaviour (Ctrl-T opened 2 tabs instead of one, but closing 1 made the other disappear, too, but I believe this is a different bug) IMHO, tab browsing has become broken to the point of uselessness. This bug MUST be fixed before releasing a new version. Personally, I will go back to 20021202. All later nightlies I've tried were less stable in one respect or another.
*** Bug 197795 has been marked as a duplicate of this bug. ***
*** Bug 194393 has been marked as a duplicate of this bug. ***
I've found a way to reproduce the problem 100% on my machine with Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3) Gecko/20030317 (the official 1.3 release) Select Edit/Preferences then immediately close prefs again with "Okay" and middle-click on any link (middle-click being set to open link in new tab in the background, i.e. all checkboxes checked in the Tabbed Browsing section of the prefs). The new tab that is created is a broken tab. And there seems to be a new phenomenon, too (at least I haven't seen this in earlier builds). If you do Edit/Preferences again after creating such a broken tab, Mozilla crashes.
As this seems to have turned into a crash bug that's very easy to hit now, I think Severity should be upgraded to "major" (once someone else has confirmed my observation).
I'd like to clarify my report in comment 81. It's not a crash in the sense that Mozilla terminates right away. Mozilla's CPU usage goes up to 99% and memory usage keeps growing like it does when you hit bug 174473. Deleting XUL.mfasl doesn't fix the problem, though. I didn't wait for Mozilla to reach OOM, so I don't know if it would catch itself.
Flags: blocking1.4a? → blocking1.4a-
Re comment #81 to 83: I cannot reproduce the problem with your steps. Neither do I observe the hang/freeze you reported as "crash". Is it a specific page you load by middle click? Have you set new tabs to open in background or not?
re comment 84: No, it doesn't matter which link I click. I've tried links on www.mozilla.org and www.freshmeat.net. As I've already said in comment 81 I have all checkboxes checked in the Tabbed Browsing prefs section and use middle click to open the link in a new tab. Have you tried it with the exact same version, i.e. Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3) Gecko/20030317 ? But in any case the problem happens so frequently with this version that you should have no trouble creating broken tabs. I can't use it for 5 minutes without getting at least 1 broken tab. I have one right now (created with Ctrl-T this time, not middle-click). As I've already said something must have changed significantly since 20021202 where this problem is very rare. I have a relatively slow computer (in Slozilla-terms), a 500MHz K6/2. Maybe the bug is a race of some kind that his harder to hit on faster machines. This would make sense as I also notice a significant (and annoying) slowdown of the Preferences UI compared to 20021202. Maybe some change introduced a slowdown that is now responsible for exposing this bug more often.
Re comment #85: I tried 2003032408 on Win2k. Not exactly the same build date, but since you see this since December that shouldn't make a difference. But yes, I did not test the Linux version and my Computer is an Athlon 2600+. For the timing issues I tested Mozilla 1.3 on a Athlon 600, but could not reproduce any of your problems. Maybe I'll have a chance to test it on Linux soon...
While problem exists to a lesser degree in older versions, it is not reproducible there, so for reproducing I suggest you try the sources from http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.3/src/
More observations: 1. background loading is not required for reproducing the problem. I turned it off and can still reproduce it. Same goes for hiding of tab bar when only one window is active. 2. broken tabs ALWAYS load in the background, even with background loading disabled. They do not get activated after creation, unlike normal tabs. 3. Right after I start up Mozilla (configured to start up with an empty page) I already have the following message in the Javascript console 2 times: Error: can't encode principals (failure code 80004005) 4. After I select Edit/Preferences, even before the Preferences window pops up ("fortunately" it takes a few seconds to come up so that I can switch to the JS console before it does), the above message appears for a 3rd time
I've done some tests and I think I've cornered the problem. tabbrowser.xml contains the following statement at line 670 (in function addTab()): var b = document.createElementNS( "http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul", "browser"); Later, at line 708, there's b.webProgress.addProgressListener(filter, Components.interfaces.nsIWebProgress.NOTIFY_ALL); Now the problem is that apparently the properties of b, namely b.webProgress are not available immediately after b's creation. According to my observations b.webProgress is never available until after the statement this.mPanelContainer.appendChild(b); in line 693. However, and this is the problem, even after this statement, b.webProgress is sometimes not available. It looks like whatever makes the webProgress property available is competing with the execution of the function addTab(). Under some circumstances webProgress is made available before addTab() is permitted to complete. In that case everything is fine. Under other circumstances however webProgress is not available when the execution flow returns to addTab(). This causes b.webProgress.addProgressListener(...) to throw an exception. This aborts tab creation halfway through (resulting in a tab that has no proper title, no content and does not go to the foreground even when background loading is disabled). Because the corresponding removeProgressListener() call in removeTab() also throws an exception (the progress listener has not been added after all), the function removeTab() also exits with an exception, preventing the tab from being closed. Regarding the race condition: Apparently there is not really parallel execution between whatever is responsible for providing the webProgress property and the code of addTab(). So it's not really a race. The behaviour is deterministic (as I reported I can reproduce this problem 100%). Furthermore, wait loops inserted after this.mPanelContainer.appendChild(b); do not make a difference no matter how long they are. So this is not a timing issue. The problem is that under some not timing related circumstances (e.g. right after I have opened and immediately closed the Preferences window) the execution flow returns to addTab() too early and once it has returned to addTab(), addTab() is not interrupted anymore. UNLESS I insert an alert(), that is. If I insert an alert() somewhere after this.mPanelContainer.appendChild(b); but before b.webProgress.add..., then apparently addTab() is interrupted and the initialization of webProgress is allowed to complete. With an alert() after this.mPanelContainer.appendChild(b);, webProgress is always initialized and broken tabs do not occur. I have also managed to prevent the creation of broken tabs by splitting the addTab() function in two parts, executing the second part after a 0 timeout. This also supports my theory that this is not a case of separate threads competing for CPU time that depends on timing but rather some deterministic issue with scheduling of code execution in a single thread. When I said "broken tabs" in the previous paragraph I was referring to tabs that can't be closed. The closing problem is what this bug is about, however, there is a second problem also found in the reports for this bug, that is related. There are problems with the tab label (it doesn't update properly to reflect the page title and instead shows a URL). This problem remains even when I resolve the webProgress issue as described above. My guess is that a problem similar to the webProgress issue exists with regards to the statement b.addEventListener("DOMTitleChanged", this.onTitleChanged, false); at line 695. I have not investigated this further. My conclusion is that to fix this bug, a way must be found to ensure that this.mPanelContainer.appendChild(b); does not return until b.webProgress has been properly initialized. Something similar will probably have to be done to fix the broken tab label issue.
We must add some debug info like this: file: tabbrowser.xml line: 693+ this.mPanelContainer.appendChild(b); + + var tabs = this.mTabContainer.childNodes.length; + var browsers = this.mPanelContainer.childNodes.length; + if (tabs != browsers) { + alert("ERROR:\ntabs = " + tabs + "\nbrowser = " + browsers + "\nPlease add your findings to bug report 13477"); + if (tabs > browsers) + this.mPanelContainer.appendChild(b); + else + this.mTabContainer.appendChild(t); + } + if (tabs != browsers) { + alert("ERROR:\ntabs = " + tabs + "\nbrowser = " + browsers + "\nPlease add your findings to bug report 13477"); + if (tabs > browsers) + this.mPanelContainer.removeChild(this.mPanelContainer.lastChild); else this.mTabContainer.removeChild(this.mTabContainer.lastChild); this.addTab(aURI, aReferrerURI); } b.addEventListener("DOMTitleChanged", this.onTitleChanged, false);
Why do you think this is helpful? If you're referring to the issue that the tab bar disappears when "closing" an unclosable tab and then reappears with the tab still there, this is not caused by inconsistent counts. The hiding of the tab bar is done when this.mTabContainer.childNodes.length==2, i.e. it's triggered by the number before the close. IOW, the tab bar disappears but the count remains at 2 because the exception happens before the remove operations. I don't see the potential for these 2 numbers getting out of sync in the code. Have you observed them differ? BTW, you forgot a digit in the bug number.
Mozilla 1.4a, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401, Windows XP build 2600.xpsp1.020828-1920 just grabbed 1.4a today and have noticed a number of bugs already, including a jinxed tab on the first day. :( Fwiw, this browser session that I'm experiencing the jinxed tab in was not begun normally*. To see what I did to get this browser session up and running, please read bug 191872 comment 10. Note in that explanation that I am not able to bring up new tabs in this browsing session w/ either Ctrl+T or the Open New Tab button, instead I have to right-click on a link and open the link in a new tab (which opens in the background, btw). Some things I should add to this report are the following JavaScript Console warnings/errors associated w/ the jinxed tab. At first, when I go from a non-jinxed tab to the jinxed tab w/ a mouse click on the jinxed tab, I get the following warning in the JS Console: Warning: reference to undefined property this.mTabListeners[this.mPanelContainer.selectedIndex] Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.updateCurrentBrowser() Line: 21 However, strangely, after closing one of the non-jinxed tabs (which was opened before the jinxed was) I no longer get the above warning. :\ Trying to close the jinxed tab results in: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab() :: removeTab :: line 32" data: no] Another sour note: When I click on a link in the jinxed tab, the back button is still greyed out and Alt+Left does not go back in history, although the Go menu item shows the items in browsing history that are available & selecting the past history items navigates to said item. Also, you can right-click on the greyed out back button and select from the history. Please read my comments in this bug to see *exactly* what I'm experiencing in this jinxed tab: bug 126826 comment 121 bug 126826 comment 122 bug 126826 comment 123 bug 126826 comment 124 bug 126826 comment 126 bug 126826 comment 129 This error appears in the JS Console when using Back button in jinxed tab (if you've read the comments above in bug 126826, keep in mind that it only appears when using the Back button [when I can] and not the Forward button) and also appears if I click a link in the jinxed tab or select Go>[any item in tab's browsing history]: Error: listener has no properties Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.onLinkAdded() Line: 36 frustrating...if anything else comes to mind that hasn't already been shared, I'll append it here. :(
*** Bug 190779 has been marked as a duplicate of this bug. ***
*** Bug 201970 has been marked as a duplicate of this bug. ***
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030617 I can't close empty tabs with ctrl-w. I think it also is the same in win98. I get those empty tabs when I fetch a pdf-file with a click on the middle button, e.g. open in background tab. Then you normally get a 'residual' empty window, that is not closeable with ctrl-w. Clicking the 'x' in the right corner works fine.
I'm having the same problem as #38 on this bug. Sometimes when I right-click on a link and Open in New Tab, a new tab appears with the title of (Untitled) and is blank. At that point, I'm unable to close the tab nor make it go away without closing the entire window. Other tabs within that window work fine, but usually once I hit this problem, attempting to open new tabs gives the same result.
Any progress on this one? It happens every time I use mozilla, even with 1.4. After som browsing, I get one or more "(Untitled)" tabs, which can't be closed without closing the whole window. When mozilla is in that state, often loading new pages in new tabs isn't working (they become "(Untitled)"-tabs before loading properly.
For what it's worth, this doesn't seem to affect Firebird. I said back in comment 55 that it was happening in Phoenix, but it's been many, many months since I've seen it since, and I use rediculous amounts of tabs. I suspect Firebird has either fixed it, or doesn't trigger it at all.
I don't see this at all anymore. I'm using 1.5b but I don't recall it showing up for a few months.
I had it happen with 1.5a on NT.
I am having this problem in Firebird 0.6.1 runningf Windows 98. I am also using the Tabbrowser extension but its' a relativley new version (past 2 months). In my case, all of the tabs looked grayed out, the x doesn't work, but Control-W does. It seems to happen when I have a bunch (> 5) tabs open and I accidently click on the bookmarks toolbar instead of a tab. If I close out and restart the browser, everything is fine. This happens almost every day since I tend to mis-click a lot.
I use the tabbrowser extension and the phenomenon seems to occur here as well. The tabs cannot be closed after a page within that tab has been fetched as a result of a form posted with the POST method. HTH. Marc
The problem seems to be gone on Linux after I updated to CVS Version 2003-10-15 and the recent Tabbrowser Extensions. HTH.
I've had this happen to me too... Where there's 1 or more tab(s) that cannot be closed, no matter what level of trickery is appilied to the task of closing the tab. Very unpredictable. It doesn't matter which side the tab(s) in question is/are on, therefore it's not a tab getting excluded from a count somewhere. Other than the tab not closing, it's completly normal and usable. This condition seems to 'spread' to other nearby tabs when you try to open a page in them, or when you try to open a page in the affected tab. It may have something to do with the tabbrowser extension, as it only seems to happen with it installed. I haven't checked in the JavaScript console while this was taking place, nor have I recieved any indication of any JavaScript errors, though I'll remember to check the next time this occurs. This bug gets a vote.
Flags: blocking1.7.x+
I investigated a bit about the causes of this problem, and I found that I had installed the "undoclosetab" extension in previous version (1.7.2). The javascript console gave a hint that something was wrong with the extension and the new mozilla version (1.7.3). In the end, I just removed the chrome directory from my profile, resulting in a working tab set (but no extensions or skin). Sorry for the inconvenience about the previous post. Hope this information helps.
Flags: blocking1.7.x+
Firefox 1.0.2, Windows 2000 + SP4 Middle click (to open window in a new tab) a mailto-link (found for example from this page). It will open a new tab and that tab can't be closed (tried everything I know), unless you close thw whole browser window or if you open a new valid tab, which seems to unlock the situation. Can someone please try to verify this behaviour, because this seems to be a very easy way to reproduce the bug.
(In reply to comment #106) Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050319 Firefox/1.0.1 StumbleUpon/1.9993 (Debian package 1.0.1-2) If that is the case, Reijo, then your steps seem to demonstrate the bug due to a more recent regression. I could not reproduce the behavior following the steps given, nor have I been able to reproduce it for quite some time now in any of the Mozillians. Alex
(In reply to comment #106 and #107) Further investigation shows that the behaviour seems to occur only if you have mouse gestures "All-in-one Gestures 0.12.4" extensions installed and enabled with Firefox. Should this be counted as a bug of the extensions or should Firefox not allow this kind of locking?
(In reply to comment #108) All-in-one Gestures 0.13.4 seems to fix it, since with that version, tabs are closable.
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8b2) Gecko/20050412 Firefox/1.0+ Starting to see this again after not seeing it for a year. The only extensions I have installed are Flashblock, Translate, and FoxyTunes. Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml :: removeTab :: line 1151" data: no]
*** Bug 296505 has been marked as a duplicate of this bug. ***
*** Bug 318497 has been marked as a duplicate of this bug. ***
*** Bug 329365 has been marked as a duplicate of this bug. ***
Still having this problem with FF 2.0.0.1...
Hi, okay same thing on version Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1. I got this error in this case: 1. Open mozilla.org (new window -> no other seamonkey opened) 2. Open in same tab bugzilla 3. Create account 4. Open new tab for my gmail account 5. Open new tab with activation link 6. i go on 1st tab (bugzilla tab where i insert my email account to register) and cannot close the tab: used (X) button in right top corner to close the tab, right click on the tab select "close-tab". unless i press ctrl+w that closes everything else except the window i want to close. Another thing it's that the url of the tab that it's locked or something it's not valid, i mean it's not the url of that tab, it's the url of the previous tab that i switched from. Another thing, you cannot start a new seamonkey window unless u close the seamonkey window with the locked TAB. Another thing, menu from the seamonkey quicklaunch tray icon on right click the item "Exit seamonkey" it's disabled, and also opening a new seamonkey from quicklaunch it's not opening the window. In the 1st case i thought that the problem came from the Quicklaunch module, but i made a few more tests without quicklaunch and it manifests the same. I just hope u can get this bug fixed :D
I had the same problem today. I cannot provide a detailed list of steps to reproduce the error but I've got the errors that were logged to the console: Error: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.canGoBack] Source file: chrome://navigator/content/nsBrowserStatusHandler.js Line: 300 Error: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebProgress.removeProgressListener] Source file: chrome://global/content/bindings/tabbrowser.xml Line: 1154 I'm using SeaMonkey 1.1.1 - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1
This bug is very annoying. Is there any developer taking care of this? Here's my way to reproduce this bug - certain tabs cannot be closed by clicking on the X sign from the tab's right corner: 1.Login to google reader (http://www.google.com/reader) add some rss feeds and open an article by clicking on its name in the right pane. 2.A new firefox tab is opened and you can read that article 3.Now try to close that tab by clicking on its X button or right click on that tab and click "Close Tab" - it just can't be closed! From error console: "Error: originalRemoveTab is not defined Source File: chrome://allinonegest/content/gestimp.js Line: 174"
do you have same problem with seamonkey trunk? ftp://ftp.mozilla.org/pub/seamonkey/nightly/latest-trunk/
My firefox does this as well. It isn't always the same site or anything and it happens randomly. The next time it happens I will copy the error console entry and paste it here.
From time to time I encounter the problem, but till now I could not see any pattern when this happens in FF 3. Before I switched to FF 3 I did not encounter this problem in FF2
(In reply to comment #120) > Created an attachment (id=327087) [details] > This is a screenshot from Firefox 3 in the case when there is no close icon for > the tab > > From time to time I encounter the problem, but till now I could not see any > pattern when this happens in FF 3. > > Before I switched to FF 3 I did not encounter this problem in FF2 > For myself it was the opposite. I had it on FF2 but since switching over I have yet to see it and I have had FF3 since its official release.
Manuel mkreft@drk-hille.de, what you see might be a window.open redirected in a tab, with close feature disabled or somesuch. With the original bug here, the tabs had close buttons, they just didn't work (neither did any other action to close the tabs, apart from closing the whole window, with all tabs).
Product: Core → SeaMonkey
I've been having the same problem. One tab, (the first one), will not close nor will it update the url in the address bar when I go somewhere else. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16
Assignee: jag → nobody
QA Contact: pmac → tabbed-browser
I also suffer from this problem, but the number of occurrence is more than that of before. I don't have any idea about the cause for this problem. When this problem occur, the title of the tab won't change, can't close it via close tab and close other tab (tab that can't be closed via the close button or ctrl + w still remain here) Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Since SM2 no broken tabs here.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: