EXCEL.EXE *32 stays open inTask Manager when Excel is closed

[Mvaldesi]

Good afternoon,

While I’ve not been able to pin down when or why this happens, occasionally, upon opening and subsequently closing an Excel workbook, EXCEL.EXE *32 still shows to be an active process in the Task Manager. If I then open a new session of Excel, a second EXEL.EXE *32 process shows up in addition to the initial one. Troublesome enough, but what’s worse is that the initial process begins to accumulate memory usage from the second process as well as the memory resources it already had locked up. When I first caught this, I had an EXCEL.EXE *32 process that was hogging nearly 1.4 GB of memory, effectively grinding my machine to a halt. Now that I know this happens, I have to check Task Manager several times a day, after opening and closing multiple Excel workbooks, to kill this phantom Excel memory eater. This has worked for the most part, but I’d like to know why this is happening and what I can do to stop it. Little help??

Thanks!

[mehmetcik]

Read this Article: http://www.tushar-mehta.com/excel/vba/xl_doesnt_quit/

[Mvaldesi]

Thank you for your response!

I’ll admit, most of that article is above my head. I don’t do anything in Excel VBA; I do everything using the frontend tools of the application. What might I have done on the frontend to create a “global” reference and where might I look to identify whether or not this is the issue?

Thanks!