Closed Bug 186099 Opened 22 years ago Closed 21 years ago

tabs not rendering after opening and closing many tabs

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 193011

People

(Reporter: jptech, Assigned: jag+mozilla)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126

I use tabs instead of windows, I open and close them frequently.  after approx.
60 new tabs, new tabs won't render, all existing tabs won't render unless they
have java or flash applets.  tray icon disappears and after closing and opening
a new process of mozilla, the right-click, open in new tab no longer functions.
 I must ctrl-click to open in a new tab.

Reproducible: Sometimes

Steps to Reproduce:
1.  open a new tab, then open and close many new tabs by either, ctrl-click or
right-click, open in new tab.
2. 
3.

Actual Results:  
after a while maybe 60 tabs, the new ones won't render and the old ones won't
render either.  tray icon disappears and after closing and opening a new process
of mozilla, the right-click, open in new tab no longer functions.

Expected Results:  
should have opened a new tab and rendered it normally
confirming with win2k build 20021218..

I opened 119 bug reports (from todays bug list) in tabs.
after x tabs they are emtpy.
I got a few errors in teh JS Console but i don't know if they are related :
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIBrowserBoxObject.docShell]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://global/content/bindings/browser.xml#browser.docShell (getter) :: onget
:: line 0"  data: no]
Severity: critical → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: tabs not rendering after opening and closing many tabs → tabs not rendering after opening and closing many tabs
and i can't close this empty Tabs. I get 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]
See also bug 156405 and bug 193011. I'm not marking the duplicate because I'm
not certain it's the same problem, but this probably will be fixed when I fix
bug 193011. Marking the dependency, because they are at least related. What
happens is that there is a sanity-check on the number of docshells, to prevent
frameset recursion, that is being mistakenly applied to chrome docshells.

Please test 1.3b to see if this problem has been lessened at all by my checkin
in bug 156405.
Depends on: 193011
dup of bug 137477?
*** Bug 193221 has been marked as a duplicate of this bug. ***
*** Bug 206322 has been marked as a duplicate of this bug. ***
*** Bug 209636 has been marked as a duplicate of this bug. ***
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

I have the same problem: after opening about 20 links from a link list with
ctrl+shift+click, closing some of them and opening again about 20 tabs the are
some tabs with the title "(untitled)". it is impossible to load another url in
it or to close them. opening new tabs makes no problem, but the untitled tab is
still here until I close the whole window.

The links that i load are all from different servers
Is this a problem with 1.5rc1 builds?
In particular, the patch for bug 193011 was checked in on the 1.5 trunk....
till now, i never had the described problems in mozilla 1.5 (release)

good work :-)
should be fixed with bug 193011

*** This bug has been marked as a duplicate of 193011 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
*** Bug 176055 has been marked as a duplicate of this bug. ***
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.