IIS leaves a zombie process after an unmanaged exception

Hi,

I'm administering this application (written in C++ with ATL) running under IIS 5 in ISOLATED protection level. Sometimes (the provider doesn't yet know why), it throws an unmanaged exception. So Windows "kills" the process...well, watching the corresponding DLLHOST process with the Process Explorer, Windows unloads every dll loaded in the DLLHOST process, but it leaves the process "alive" with this files:

Unicode.nls

Locale.nls


Sortkey.nls

Sorttbls.nls

Ctype.nls

R000000000967.clb

The problem is that I've to kill the process with Task Manager, because even if I take the site down, IIS doesn't wipe this process. And what is the worst: IIS keeps receiving connections for this process, so if I didn't realize that the application was hung, connections keep increasing and lowering the server performance.

I know that the provider has to manage the exception, but I would appreciate a hint about why Windows(or IIS) doesn't completely clean this DLLHOST process after the unmanaged exception occurs.




Thanks,

Federico

I don't know what to suggest other than fix the code so it doesn't throw errors.