It has nothing to do with content. Memory can factor in, but the likely culprit is a lack of support, by your video card, for particular OGL extensions... namely a transparency buffer. Partial implementations of the OGL spec certainly don't help either, especially considering we're writing against the spec. Will we work around the limitations of the card? We've already tried to include a number of fallbacks, in the event an extension is not supported by the card, and we'll continue to refine them as needed, but there comes a point where a particular card (or series of cards) just won't cut it. D|S creates a 'log.txt' in its root directory. Amongst other things, recorded in that file are the extensions your card supports, and which of those D|S is using. Reporting the issue and including that file will help us identify the problem.

FWIW, at home, my current primary machine has a GeForce4 Ti4600 128MB... I've not had a single problem. I also have a PIII 733MHz Dell Inspiron 5000e (laptop) with a Rage Mobility 128 M3 16MB, which has been relegated to continue the rest of its life as a glorified email client, but I see the same widget display issue on it. At the office, one of my machines has a Radeon 8500 128MB... and with each driver, new/different problems occur in ALL applications I use which utilize OpenGL, not just D|S. ATI's drivers have been... well... annoying, to say the least. I'm in the process of migrating to a new machine at work... one with a GeForce FX 5600 256MB card. Like I said, FWIW.

-Rob