Archived

This topic is now archived and is closed to further replies.

.X file IDirectXFileEnumObject::GetNextObject() memory leak?

This topic is 5021 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

After days of wondering why Windows task manager keeps showing an increase in my program''s memory usage whenever I invalidate and restore my 3D objects, I have finally tracked it down to IDirectXFileEnumObject::GetNextObject(). The memory usage goes up when my program is in the GetNextObject() loop (Procedure is described in http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dx81_vb/directx_vb/Graphics/Reference/VB/XFile/classes/DirectXFileData/getnextobject.asp). However, memory usage does not go down even after the IDirectXFileData object is released. I took a look at DirectX8.1 SDK .X loading sample and the same seems to be true. Memory usage keeps getting higher with each .x file I load even if it is the same one again. Memory usage goes up by 100-300K each time. Is this normal? Thanks. ^_^ _________________ Best regards, Sherman Chin Director Sherman3D (Malaysia) Sdn Bhd www.Sherman3D.com chat.Sherman3D.com forum.Sherman3D.com www.VibeForce.com

Share this post


Link to post
Share on other sites
I just got a reply from the mrgamemaker.com forum:

"
In DX8 I always found a memory leak when loading skinned meshes. I can''t
remeber if I ever tracked down the offending function, but it was there in
my implementation, and the SkinnedMesh demo as well.

This prolem seems to have gone away in DX9.

I dont know if this is the same problem, but you should migrate to DX9
anyway, it is definitely worth it.

Apparently DX10 will not appear until well after the new version of Windows
is published, so it is not a futile exercise.
"

so I guess I am not alone in this. Or has everyone really moved on
to DX9 already...or never bothered using .X skinned mesh files?


_________________
Best regards,
Sherman Chin
Director
Sherman3D (Malaysia) Sdn Bhd
www.Sherman3D.com
chat.Sherman3D.com
forum.Sherman3D.com
www.VibeForce.com

Share this post


Link to post
Share on other sites
I have been advised in the Microsoft DirectX mailing list
to upgrade to DirectX 9 to solve the problem. However,
I would really love to know if someone has found a solution for
this in DirectX 8.1 yet or has encountered such a problem
before. Thanks. ^_^

_________________
Best regards,
Sherman Chin
Director
Sherman3D (Malaysia) Sdn Bhd
www.Sherman3D.com
chat.Sherman3D.com
forum.Sherman3D.com
www.VibeForce.com

Share this post


Link to post
Share on other sites

Share this post


Link to post
Share on other sites