At 12:09 PM 9/17/00 -0700, you wrote:
<snip>
>I haven't hacked at Wine much, but I've been seeing some messages lately
>that some major changes to the way that GDI objects are allocated have
>been taking place. I assume this is due to those changes. In
>particular, the messages about Wine now only being able to allocate
>about 1000 brushes/pens/DCs/etc.
<snip>
I never wrote something like that 'now'. There is nothing new in this limitation.
The recent change has nothing to do with it, it was only aimed at having
a better control of access to these object handles. AFAIK there are no
bugs remaining related to this change.
Leaks can be triggered by many things; for example, a change in the
Wine code may cause the app to pick an execution path where it's really leaking,
that is, a real bug in the app.
I have seen something like that with an app where it was leaking in some
(unfrequent) configuration. After searching Deja I found that the problem was
also happening under Windows. Fixing a problem like that can be pretty
difficult since the Win32 api is not deterministic - the message execution
order is not generally specified in the documentation, so forcing the
execution path to fix a particular application can be actually a bad idea
and break other apps.
Also, the leak can of course occur because of a change in Wine.
In this case, you can try to debug by the usual ways :
- regression : use cvs. There is a procedure for that in the documentation.
The patch you are referring to was committed just after the 20000821 release.
- normal search : debugmsg +gdi,+relay. If you follow this list details
have been several times posted to give tips on how to change the Wine code
to better debug this kind of problem. The appropriate channel for that is the
cemw news group IMHO.
Gerard
