LOCAL: Not enough space in GDI heap
Cenedese at indel.ch
Mon Feb 9 04:23:39 CST 2004
>>> Now is this an error in my application (VB6 with lots of controls and ocx's)
>>> or one in wine? Does my app really create so many fonts or should each
>>> only appear once in this list because they're all the same? They do have
>>> different handles/addresses but that could be wine too. Of course it works
>>> on Windows but that could just be pure luck :)
>>> Is there some way to tell on Windows if it really uses so much GDI heap?
>>> Being a VB app it's not that easy to debug low-level.
>>If you work with Win2K/XP, you can use NTobjects a free tool from
>>www.smidgeonsoft.com. It shows you for each process the number of each
>>type of GDI objects, compare that with the number that you observe in
>>your wine logs.
>That's a nice page, interesting looking tools. I tried it out and if the app is
>running it has 39 fonts and the other items (Pen, Brush, Bitmap) even less.
>So this looks like wine reserves unnecessarily too many fonts. I'll see if
>I find something more.
After fiddling around and creating some test programs I found that in wine
a font is created for every control. Even a simple dialog with just four labels
or textboxes in it will have 4 times a MS Sans Serif font. So this looks like
another problem concerning wine and VB (Man, I hate this VB...). On Windows
it uses only one font MS Sans Serif. As my original application which I want to
make work uses many dialogs and controls it's now obvious why it runs
out of GDI memory.
I'm now trying to find out who decides if a new font has to be created or
if an old one can be used. If anyone knows about this (in VB) please
let me know.
More information about the wine-devel