The Edraw Office Viewer Component V5.6 fixed the bug which the component closes the Excel document (but leaves Excel running) if I have Excel open in another window. Fixed the bug which The Excel process in background is still running and not terminated actually.
2 Responses to “Kill dozens of Excel.exe processes stacking up in Task Manager”
Leave a Reply
You must be logged in to post a comment.
February 20th, 2009 at 8:23 am
The new component allows the user’s computer has the excel instance before use the component. But when the user is using the component, it dosn’t allow to lanch new excel instance from destop directlly.
December 8th, 2009 at 3:03 am
This is because ExcelIS COM and COM does not have the easy garbage collection that comes with Java/.NET.
Each COM object uses a Reference Count and until the reference count is 0,
the COM object will never get out of your RAM. So how then do you reduce the reference count to 0.
By setting every COM object reference to NULL. This is not only the Document and Application.
You can overload the BeforeDocumentClosed event.
OA1.ActiveDocument.Close(); OA1.ActiveDocument = NULL; OA1.Application.Quit(); OA1.Application = NULL;
Or try the Garbage Release.
public void OnDisconnection(Extensibility.ext_DisconnectMode
disconnectMode, ref System.Array custom)
{
Trace.WriteLine(“OnDisconnection”);
System.Runtime.InteropServices.Marshal.ReleaseComObject(applicationObject> applicationObject =null;
GC.Collect();
GC.WaitForPendingFinalizers();
GC.Collect();
}