exactly.

People who have no clue how computers work have no business proposing their idea of what's going on.

Arch Magi is right -- this is Turbine's problem, and it's not related to the version of DX.


C++ emory leaks can stem either from new/delete or malloc/free.


DX surfaces and textures are COM objects and are deallocated from either video memory (default pool) or system memory (managed pool or offscreen plain textures/surfaces) when their reference count drops to zero or the device gets reset (for video memory objects only). There's no real way to leak a texture, the most you can do is hold a reference until the program closes. But that's entirely different from leaking, as the texture is still in a usable state somewhere.


Lil-Blub: now please go away until you learn how to program. You don't know ANYTHING about how computers work, so keep your mouth shut.

 

-----signature-----

As said..." I am beginning to wonder if.... "


Your welcome though master, I still love you and your crew still. I am sorry this is getting alot of attention and your not.


*edit*

Date Posted: 5:41pm Subject: RE: Everyone having issues with AC Client using alot of memory click here: - Date Edited: 5:42pm (1 edits total) Edited By: Hazridi

People who have no clue how computers work have no business proposing their idea of what's going on.

Arch Magi is right -- this is Turbine's problem, and it's not related to the version of DX.


C++ emory leaks can stem either from new/delete or malloc/free.


DX surfaces and textures are COM objects and are deallocated from either video memory (default pool) or system memory (managed pool or offscreen plain textures/surfaces) when their reference count drops to zero or the device gets reset (for video memory objects only). There's no real way to leak a texture, the most you can do is hold a reference until the program closes. But that's entirely different from leaking, as the texture is still in a usable state somewhere.


Lil-Blub: now please go away until you learn how to program. You don't know ANYTHING about how computers work, so keep your mouth shut.

Make sure I don't have any time to edit. 12 mins guys. THEN respond.

 

-----signature-----

I know... an attempt to "help" turned on me once again because of the Decal Devs.


I apologize I don't know how to code, and I am not as good as Haz is. He again rules this world cause he can code.


Egotistical arse hole.

Your 'attempts to help' would be better labelled as misinformation, random conjecture, fearmongering, or trolling. End of story.

 

-----signature-----

Your 'attempts to help' are appreciated. You may have been wrong but the attempt was welcomed. At least you are trying.

And indeed, in the absence of other information, this is an entirely plausible cause. There are plenty of ways to "leak" (in the coloquial sense) other than failing to delete memory from the free store. The DirectX objects are allocated in process, and will certainly contribute to the overall memory usage - failure to release will effectively be a leak.


These leaks can also occur not only within userland code, but within DirectX itself (it the Dec update fixes any, it would not be the first time it's happened). A good suspect are the D3DX libraries, which are effectively just consumers of the DirectX core interfaces, and deal with what always used to be application level problems; any flaws within these could certainly cause a leak within the client, and these flaws could be fixed with an SDK update.


Now, as it happens, it doesn't appear that this is the problem (the preponderance of evidence pointing in other directions). But this doesn't stop the original suggestion being valid, and worth exploring.


I'd make a comment about people in glass houses, but don't really want to start a flame war.

Dont get your panties in a bunch Hazridi, its harmful to your health.

 

-----signature-----