even though my pc has more than 200 megs of ram, it usually has low system resources. if i launch apprunner and load test number 10, this is what i often see (that's a windows bitmap image of apprunner). it often crashes before or after i see this kind of thing. i understand that this might not be fixable... but what do we do when there are not enough system resources available to draw things correctly?

This looks more like a layout problem than an image problem. Does this problem still exist with the current tip build? -pn

Since viewing bmps is currently not as convenient as jpg, I've moved the test URL at http://schist/ngimage.bmp to http://jazz/users/pnunn/publish/ngimage.bmp and put a jpg copy in the same location. The display area is not really looking at an URL, right? There's nothing in the URL bar. So if the display area is filled with garbage from previous displays, we need to clean up the display. If I'm misreading the bug, and the chrome display is overwriting in the content window, we have a different problem. Troy: Could you take a quick look at this and tell me if low mem could screw up the display layout? I'm reassigning to you so it will ping you. Reassign to me if it is a weird variation on bug#1248.

Pam, no layout doesn't really care about low memory, especially low system memory. Considering that demo10 involves alpha blending and compositing I'm changing the component to Compositor. It's possible that maybe one of the off-screen resources couldn't be allocated? BTW, this bug doesn't say which OS it applies to, and it really should. I would be amazed if this is happening on NT, so I would expect it is a Win95 or Win98 problem

d'oh! troy guessed correctly: this was seen on a windows 98 system. i have not seen this problem under nt.

Kevin can you take a look?

Moving to M11

Moving to M13

Moving to M16

Moving to M18

There have been many improvments to the management of the offscreen bitmaps used by the ViewManager + plugging of GDI leaks. Is this bug still valid?

This bug is marked "future" because it is not critical for RTM (Release To Manufacturing). If anyone believes it is critical, please explain why in this bug.

There have been a number of improvements in this area, so this should no longer be an issue. Marking FIXED.

Marking verified per last comments.