🚀 go-pugleaf

"MWP" <mwp@overclockers.com.au> wrote in message
news:3f12ee7f$1@newsgroups.borland.com...
>
> Hi all...
>
> Is there any special way that threads need to be handled in DLLs?
>
> Ive found that if my app loads a DLL that uses threads, other windows
software start to have problems.
>
> If my app loads a DLL that doesnt have threads, the problems dont occour.
>
>
> The problems are for example:
> Some applications wont start until my software ends (Explorer does this).
> Some applications wont show dialogs until my software ends.
>
> Maybe my DLLs with threads is somehow stopping other applications from
being able to create threads??
>

Creating threads shouldn't be enough to cause the problems
you're seeing.  I'm guessing your DLL is maxing out some
system resource, such as CPU time, memory, etc.   For
example, if it creates a large number of threads that could
account for the problem.

I'm assuming you have the source for both your application
and the DLL.   If so, try to create a small code sample (i.e.
minimise the size of both the DLL and the application
that uses it) that recreates your problem.   That should help
in tracking down the problem.