On 8/20/2010 10:01 PM, Bert Huijben wrote: >> -----Original Message----- >> From: Erik Huelsmann [mailto:ehu...@gmail.com] >> Sent: vrijdag 20 augustus 2010 13:20 >> To: William A. Rowe Jr. >> Cc: dev@apr.apache.org >> Subject: Re: Thread handle leak in APR >> >> On Fri, Aug 20, 2010 at 8:30 PM, William A. Rowe Jr. >> <wr...@rowe-clan.net> wrote: >>> On 8/20/2010 1:08 PM, Guenter Knauf wrote: >>>> Hi Prathima, >>>> Am 20.08.2010 09:04, schrieb Prathima Dandapani -X (pdandapa - HCL at >>>> Cisco): >>>>> Steps used to compile Apache is as follows. >>>>> Run Setenv.cmd from the Windows-Server-2003-R2-Platform-SDK >> installed >>>>> directory >>>>> Run vcvars32.bat from VC++ installed directory. >>>> AFAICT this is the wrong order; first you need to call vcvars32.bat, >>>> then Setenv.cmd so that the PSDK paths are prepended. >>> >>> Precisely :) >> >> Will reversing the order make his leak disappear? > > Changing the order might give you older or newer .lib and .h files depending > on the exact VS and SDK versions, so it might add or hide some functions that > are otherwise unavailable. But it should never change the behavior.
Thread handles are reaped when apr_thread_join() is called, which is how you 'harvest' now-dead (or soon-to-be-dead) threads. It looks like you have a non-ASF module creating threads frequently, from the users@ list post; I didn't see a ton of dups in that list. Don't forget you have to free them, if you are the author of the module. If you are using third party modules, you keep forgetting to mention which one(s).
