ActiveXObject - Excel.Application does not release resources

Question

I have developed this script where i write on an xls worksheet.

var excelFile = "C:\\TestActiveX\\Test.xls";
function readExcelFileAndUpdateView()
{
    var w =new ActiveXObject("Excel.Application");      
    w.Workbooks.Open(excelFile);  
    var objWorksheet1 = w.Worksheets(1);    
    var name =objWorksheet1.Cells(1,2);
    if(name==null){
        name="";
    }

    var objWorksheet2 = w.Worksheets(2);    
    var surname = objWorksheet2.Cells(1,2);
    if(surname==null){
        surname="";
    }

    var str = "Name is :"+name+"<br/>Surname is :"+surname;

    document.getElementById("txtAreaXLS").innerHTML=str;    
    w.Application.Quit();
    w.Quit();
    w = null;               
}

The problem is that when this function finishes execution, I have 2 EXCELL objects running in my Windows Task Manager. Releasing resources at the end of my function doesn't seem to be working.

I have also tried objWorksheet1.close(true); and w.Workbooks.Close(true); and w.ActiveWorkbook.Close(true); with no luck.

Does anyone have a clue which are the open Objects, and how can I get rid of them?

Although you have set w = null, you still have references to objWorksheet1, name, objWorksheet2, surname. Have you tried setting those to null, so you have zero references to any excel objects? — tgolisch, Feb 22 '13 at 15:00
if I set the references to null, then the Objects still exist in memory. `objWorksheet1=null;objWorksheet2=null;` — MaVRoSCy, Feb 22 '13 at 15:08
ActiveX keeps track of all references to itself and will only release itself from memory once the ref count goes to zero. — tgolisch, Feb 22 '13 at 15:25

score 2 · Accepted Answer · answered Feb 22 '13 at 15:24

ActiveX can have some odd behavior. You need to make sure that you set all references to the ActiveX object (and sub-objects/members) to null. In your code, you have set w = null, but you still have references to objWorksheet1, name, objWorksheet2, surname. Set those to null too. I would recommend a try/catch/finally block where you null those in the finally block.

There is a good article on CodeProject that recommends: Save, Close, Quit, null. Still, that won't matter unless you have nulled all references to the ActiveX objects & its members.

Sections 12 and 13 of this article have some good examples: http://www.codeproject.com/Articles/404688/Word-Excel-ActiveX-Controls-in-ASP-NET

ActiveXObject - Excel.Application does not release resources

1 Answers1