212702 - browser screen doesn't update

Status: RESOLVED DUPLICATE of bug 204374

(SeaMonkey :: General, defect)

Description

[Mr. Moose]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624

Periodically, the browser doesn't update the screen.

I will open a new tab, and it won't show the new tab.  If I run the pointer
across the tabs bar, it will update, but the contents of the window will not. 
Sometimes it will show up, other times I have raise another window above the
browser and move it about the window.  When I close the tab, it also won't
update.  Often the back/reload/etc buttons will only update when I pass the
pointer over them.

I've noticed that sometimes this happens when I have, say 15 tabs per window and
3-4 individual windows.  When enough of them are closed, the problem might (not
sure of the conditions when it does) go away.  I've noticed that it happens most
commonly when kazaa lite is running (it's happening as I write).  I've not
noticed it with other apps.  The first occurence of many tabs and kazaa isn't an
absolute connection (i.e. they can happen independently).

Now I've just quit kazaa lite and the update problem went away.  I've just
restarted kazaa lite and the problem resurfaced.  Now I can have the two running
together frequently without interference.  The only thing I can think of is that
they happen when I open up too many browser windows/tabs.

It shouldn't be a virtual memory error as I have 384 mb of memory and only the
two apps running.

Once the problem starts to occur, I can get both apps to run together again by
restarting the system.  It appears the issue when too many tabs are open

Reproducible: Sometimes

Steps to Reproduce:
1.I can't really be sure at this time, but start up both mozilla & kazaa and
start playing around
2.
3.

Actual Results:  
?

Expected Results:  
window update properly.

I'm sorry I can't give you any better information than this.  I'm a programmer
myself and if someone gave me this info, I'd bang my head against the wall.  If
there is something you would like me to try, let me know.  It's something I
reported to see if it's a behavior you have noticed otherwise and this is an
additional data point.

This problem has been present in V1.2 and I believe (but not sure) also in V1.1

Comment 1

[Matthias Versen [:Matti]]

Do you mean bug 204374 ?

Comment 2

[Mr. Moose]

> Do you mean bug 204374 ?

I actually did a search for the bug, but apparently used
different terms, but this does sound like the bug.

There are a few quirks that I've noticed that differ from
the bug.

This only occurs with Kazaa lite, when the problem occurs
and you quit Kazaa, the problem will usually go away.  I
can  then open up photoshop (or whatever) and the problem
won't occur (this could point to a possible bug in Kazaa
lite).

When I have the problem with too many tabs (and kazaa isn't
running) and close a few tabs, the problem goes away
(though this could describe a lack of resources and the
memory is properly returned to the heap).

All in all, sounds very similar, but hope that my
experience adds a few data points to help find the problem.
 I'll keep an eye on things to see if I can describe the
bad behavior, should you need more info or do you have
enough to work with right now?  I don't want to waste
anymore of your time.

================================

I've talked to Matthias Versen and he suggested that this is the bug#204374.  I
didn't find it in my search (as I used different terms), but I suspect that they
are closely related if not the same.

Comment 3

[Matthias Versen [:Matti]]

Thanks for your time and for your response.
I will dupe this bug now. Please reopen this bug if bug 204374 is fixed and you
still see the problem !


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