Memory leak after unreasonable ammount of DrawOverlayInGame calls and large ImageElement about direct3dhook HOT 7 CLOSED

I'd advice you to read this issue: #80
@justinstenning just fixed a memory leak, and you should also make sure your code is working correctly.

from direct3dhook.

@Vadkarika2 When you say redraw, do you mean sending a complete new overlay to the target?

Can you please provide a quick and simple reproducible snippet for the scenario?

from direct3dhook.

In my heavily modified version of this project, I wrap the code in DXSprite.cs -> BeginBatch(ShaderResourceView texSRV) with a using statement:

using (Texture2D tex = _batchTexSRV.ResourceAs<Texture2D>()) { Texture2DDescription texDesc = tex.Description; _texWidth = texDesc.Width; _texHeight = texDesc.Height; } _spriteList.Clear();

It eliminated one of a few leaks I encountered. My overlay changes each time I send it, and @justinstenning , I think this is what @Vadkarika2 is doing.

from direct3dhook.

Hi! Thanks for the help!

What I mean by redraw is I send a new overlay, yes...

I'll try out what @jazzup suggested, and post an update on the results!

Thanks again,
M

from direct3dhook.

Yep! This fixes my issue, thanks for the suggestion!

from direct3dhook.

I made a pull request (#82) where I fixed this memory leak using @jazzup's suggestion!

from direct3dhook.

Merged, thx

from direct3dhook.