Prawns:
The younger brother encountered such a problem when using the VB to write COM applications, as follows:
After the COM application registration, you cannot create success when you create an application object in the IIS application, then track the applications in COM , found that the application component is always running, you can drag, then take up 100% CPU resources, and memory In constant rise, and the programs have the same phenomenon of death, and the component is not deleted in the NT (2000) task manager, and only the VC can be canceled only by debugging.
The components created by myself have the following features:
1, the component is relatively large (more than 1m after compiling;
2. There is only one external creation of an object, and other objects are created by app;
3. Components are first registered and then import COM (the above issues will only be used in direct import mode);
4, COM compilation is: Apartment Threaded
This component only occurs when using a web application, and the chance is around 40%. Once the first use is successful, it will not appear again if it will appear again.
Under normal circumstances, the assembly is one-thousand in VB, and if the VB application is opened first (involving calling the component) first on the server, the Web application does not appear.
I don't know if you have a similar problem, what kind of solution is made, thank you.
I contact:
WANGNP@21cn.com
Jackie Wang
