when I view the processes running on the server there are two instances of dllhost.exe, one with "normal" memory usage, and one with "large" memory usage. <BR><BR>my theory is that there is something wrong with a vb .ocx component i have recently written. yes, we properly destroy all instances of that object in our asp pages. is there anything i can do to eliminate this second instance of dllhost.exe all together, or at least reduce the memory usage to something reasonable? thanks.