.............................................................................................
chlamys
collection (0) | wishlist (0)
Posts: 1
Registered: Feb '06
Date Posted: 3:55am Subject: RE: Everyone having issues with AC Client using alot of memory click here:
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.
.........................................................................................
You don't have to pull a HAZ to get your point across. Panties in a bunch is right. I was just trying to see if this could be a variable.



