Thread: Trying to solve my memory leaks

Originally Posted by h3ro

LoadTexture is in a library I dont have access to. All i know is that is take a BYTE pointer and that it should again be deleted with the array method

What is the array method?

delete[]

free()?

Mind giving us the link to the documentation?

Something weird most be happening. I can use the class functions in the Sprite class that I have created before, but if i try to add a new one, i get an error (same as before)

Code:

If I add 
void Sprite::foo()
{
// Do noting
}

and call it:
spriteList[0]->foo();

I get an error.

But if I use one of the older functions, it works fine

Maybe your sprite isn't allocating memory correctly?

Im sorry, but I cant post a link to the documentation, but it says that caller of the loadTexture function has to delete the returned data them self. And that it should be deleted using the array method.

Also, there is no deleteTexture function or something like that.

Maybe your sprite isn't allocating memory correctly?

I think it does, as I can draw to the texture without any problems. Its just deleting it that is hard.

EDIT:
What might be a reason for non of my new functions working? Like the foo() example

Code:

You'd have to post a complete, compilable example of what is going wrong - although the likely scenario is that you end up finding it yourself if you try to create this - but it's hard to guess what goes on in "..." that you haven't posted, and I suspect:
1. You are not too keen on posting it.
2. I'm certainly not keen on reading loads of code to find what's wrong.

I cant post my entire code or the needed libraries needed to compile it due to copy rights. I tried to take as much out as possible, and I can use new functions now, but I still get the memory loss even though I call the destructor for the sprites when the program closes.

Sorry for not posting the needed files, but thanks a lot for the help

Reworked the whole thing and removed a pointer that casued me nothing but trouble.

matsp: Your right, its delte[]

Its working now, with no memory leaks.

Thanks a lot to matsp and sethjackson!