Badly behaving COM object.
-
I've got a COM object that has a memory leak. This normally wouldn't be an issue except that my program is a kiosk app so it's running continuously. Using a different COM object is not an option. This is a standard visual COM object from a very large company. Rumor has it that the next version will fix the memory leak but the memory leak has been there for a long time so I'm not hopeful. So my thought is to destroy the object after a certain amount of time so that the memory will be released and to recreate it. But I can't figure out how to destroy the object other than to close the window and reopen it. Can anybody help? Thanks. Jeff.
-
I've got a COM object that has a memory leak. This normally wouldn't be an issue except that my program is a kiosk app so it's running continuously. Using a different COM object is not an option. This is a standard visual COM object from a very large company. Rumor has it that the next version will fix the memory leak but the memory leak has been there for a long time so I'm not hopeful. So my thought is to destroy the object after a certain amount of time so that the memory will be released and to recreate it. But I can't figure out how to destroy the object other than to close the window and reopen it. Can anybody help? Thanks. Jeff.
Have a second, identical window behind it and then destroy it? It's a brute-force-and-ignorance approach, but it may work if you time it right.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
-
I've got a COM object that has a memory leak. This normally wouldn't be an issue except that my program is a kiosk app so it's running continuously. Using a different COM object is not an option. This is a standard visual COM object from a very large company. Rumor has it that the next version will fix the memory leak but the memory leak has been there for a long time so I'm not hopeful. So my thought is to destroy the object after a certain amount of time so that the memory will be released and to recreate it. But I can't figure out how to destroy the object other than to close the window and reopen it. Can anybody help? Thanks. Jeff.
-
I've got a COM object that has a memory leak. This normally wouldn't be an issue except that my program is a kiosk app so it's running continuously. Using a different COM object is not an option. This is a standard visual COM object from a very large company. Rumor has it that the next version will fix the memory leak but the memory leak has been there for a long time so I'm not hopeful. So my thought is to destroy the object after a certain amount of time so that the memory will be released and to recreate it. But I can't figure out how to destroy the object other than to close the window and reopen it. Can anybody help? Thanks. Jeff.
See Marshal.ReleaseComObject[^] method, but if the memory leak is consequence of a defective programming of the COM object, maybe this will not solve the problem and, maybe, nobody will be able to solve it except for the company which developed it.
-
I've got a COM object that has a memory leak. This normally wouldn't be an issue except that my program is a kiosk app so it's running continuously. Using a different COM object is not an option. This is a standard visual COM object from a very large company. Rumor has it that the next version will fix the memory leak but the memory leak has been there for a long time so I'm not hopeful. So my thought is to destroy the object after a certain amount of time so that the memory will be released and to recreate it. But I can't figure out how to destroy the object other than to close the window and reopen it. Can anybody help? Thanks. Jeff.
I told you what to do the last time[^] you asked this. For the benefit of others, the component you're talking about is Flash, and I suggested that you need to use AppDomains to cope with this.
I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be
Forgive your enemies - it messes with their heads
