I am starting a new question rather than continuing on with the old one after working on it for over a month. Need more suggestion.
1. COM server (dllhost.exe) running vb6 code.
2. vb6 code runs .net 3.5 in proc CCW.
3. vb6 code sometimes raised "out of memory" error when createObject(.net object). It is not a real out of memory. The problem is inside the Microsoft object creation logic.
4. When it fails, we observe that the crystal report dll is unloaded (observed using procexp.exe). We are certain that this dll was loaded earlier. I believe it takes around 5-10 minutes before unloading. Nothing related to .net is inside the process space. Once .net is inside the process space, there is no failure in the .net ccw regardless of the existence of the crystal dll.
5. Restart the com+ process and load the interop first. This process will be fine until it dies.
[A] I do not understand why someone (assuming Microsoft) is unloading the crystal report dll.
[B] We know the crystal report dll is being loaded and unload. vb6 code seems running fine. I cannot assume any corruption
[C] Create object certainly is in Microsoft domain. I assume the unloaded memory makes the .net loading failed.
