Lior
June 22nd, 1999, 01:39 PM
Hi,
my very complex (Audio, Video, COM, Thread..) ActiveX works fine on debug version. On Release version on Explorer 4.0x on WinNT, it seems to leave some dlls in memory (among them winmm.dll, and some others), they are loaded by Explorer.exe, yet there's no explorer on screen (only the active desktop). It causes a crush on approx the 3rd (?!) time i load the dll. More wierd is the fact the it takes some time to load the first time i open my html, a lot faster the 2nd time, and then, the time before the crush, it asks to download and install the ocx. Then it crushes, re-start desktop, and all over again.
what can be the cause of not releasing the dlls? leaks? Missing uninitialize of something? Maybe something with the wininet?
thanks,
lior
my very complex (Audio, Video, COM, Thread..) ActiveX works fine on debug version. On Release version on Explorer 4.0x on WinNT, it seems to leave some dlls in memory (among them winmm.dll, and some others), they are loaded by Explorer.exe, yet there's no explorer on screen (only the active desktop). It causes a crush on approx the 3rd (?!) time i load the dll. More wierd is the fact the it takes some time to load the first time i open my html, a lot faster the 2nd time, and then, the time before the crush, it asks to download and install the ocx. Then it crushes, re-start desktop, and all over again.
what can be the cause of not releasing the dlls? leaks? Missing uninitialize of something? Maybe something with the wininet?
thanks,
lior