204075 - Window stops redrawing correctly after Mozilla's been in use for a while (gdi leak)

Status: RESOLVED DUPLICATE of bug 196182

(Core Graveyard :: GFX: Win32, defect)

Description

[Kim Scarborough]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030430
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030430

After I've used Mozilla for a while, it stops redrawing properly. The buttons
and borders disappear, and if I hover over a button just that button appears.
It's acting as if the machine is out of memory, but I have lots of RAM in this
box. I'm running in a really high resolution: 1600x1200. If I reduce the size of
the window the problem goes away, but as soon as I maximize it comes back. It
seems like the window is suddenly having problems going over 1280x1024. This
happens in all components.

I've actually been having this problem for as long as I've been using Mozilla,
but it's only started occurring really frequently when I went to this build from
1.4a. It seemed to happen before after I loaded a page with a lot of images, but
now it just happens after I've been using the program for a while. It's hard to
tell specifically what's triggering it.

I wouldn't be surprised if this a dupe, so apologies in advance. I couldn't find
it but I wasn't really sure what to search for.

Reproducible: Always

Steps to Reproduce:
It seems to happen after loading a page, but I can't really figure out what
combination of steps seems to make it happen. Loading a page with a lot of
images seems to trigger it sometimes, but this will happen anyway even if I
don't do that.

Comment 1

[Hixie (not reading bugmail)]

This is probably a duplicate of one of the various GDI leak bugs, although
working out which one is gonna be fun (impossible, without steps to reproduce).

Comment 2

[Kim Scarborough]

Heh, yeah, I was afraid of that. Well, I can do any diagnostic tests you guys
would like when it happens, if that would help... not sure what else to do. I'd
be glad to let a developer in my office to see it in action...

Comment 3

[Kim Scarborough]

Ha! Okay, per comment 1 I started really paying attention, and after numerous
Mozilla restarts I managed to get a stripped down test case that reproduces
every time. On my browser the symptoms I describe happen every time if the
following three conditions are met:

1) The browser is maximized on my 1600x1200 screen.
2) One tab has
<http://www.codejedi.com/shadowplan/shadow-current/manual/ReferenceGuide.htm>
loaded.
3) The other tab has
<http://www.crisisweb.org/projects/showreport.cfm?reportid=837> loaded.

It doesn't matter what order I do these steps in, but once they're all done this
happens.

Is that more helpful? I can still do more experiments if necessary.

Comment 4

[Kim Scarborough]

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