Memory Q

Do you release them explicitly ?
If you don''t, you may be in trouble as COM objects are registered with the operating system, not with an application.

Which means that they stick around even once the application has finished.

That''s why windows memory usage creeps up with uptime. Did I mention windows''s stability ?

I do release them with lpDI->Release(), but my code never makes it past this point.

So, you release them somewhere but never actuall call that code?

What''s the point? Release your objects every time!

I do call that code. I added a line above and below to write to a file saying that it is being released and that it was just released. In the file it says that it is being released, but it never gets to the line saying it was just released.

quote:

---

Original post by Fruny
That''s why windows memory usage creeps up with uptime. Did I mention windows''s stability ?

---

That seems to infer that my system''s instability is due to bad application programming? The bastards!

Whatever. chillah, do you set your pointer to NULL after releasing? Windows will clean up after your application to a certain extent, especially in debug builds, but other than tha Fruny''s comments are dead-on. Are you sure you''ve released all DirectInput devices before releasing the DI object? COM interfaces should be released in (approximately) the reverse order they are acquired.

quote:

---

Original post by chillah
I added a line above and below to write to a file saying that it is being released and that it was just released. In the file it says that it is being released, but it never gets to the line saying it was just released.

---

Use the debugger. It''s easier and better to trace execution of function calls this way.

I am absolutely positive that I release all of the DirectInput devices before releasing the DirectInput object. I think I will retry to make the whole thing and see if it will work.

Are you checking that lpDI is not NULL before calling lpDI->Release() ?

Try posting that little snippet of code so we can see if there''s a problem with it.

ok:

... Unacquire and release DI devices
if (lpDI)
{
ErrLog("lpDI was not NULL, releasing", __LINE__, __FILE__);
lpDI->Release();
lpDI = NULL;
ErrLog("lpDI was released", __LINE__, __FILE__); // never makes it here
}

ErrLog() is the function to write to a file so I can see what is going on

lpDI is the DI object created earlier

Edited by - chillah on November 26, 2001 8:27:07 PM

Edited by - chillah on November 26, 2001 11:44:35 PM

Looks okay to me, sorry I can''t help.

Are you definately flushing and closing your log file before you exit the application? It might be that the DirectInput object is being released but the line is not being being writen to file. Just a thought.

- Kaijin

"If you find a job that you love you''ll never have to work again."