ryan20fun, on 03 January 2012 - 10:12 PM, said:

I'm about to make a video if this doesn't work. How do I go about doing this?

MSVCR100D.dll is missing from the computer.

If you're using vectors then why are you using pointers?

By the way, you do not need to quote my whole post. I can scroll.

Quote

So, somehow, your code already calls delete between allocation and when you expect to free that allocated block.

So the correct approach at this point is to figure out why your code is freeing that memory when you don't want it to free, right?

The wrong approach is to switch around types in hopes the problem will go away.

It looks like you're emulating the Direct3D's use of double pointers without understanding why they do that. So in your code, I see no reason for a double pointer, yet you're using them everywhere. It's bizarre.

> so how would i keep track of the pointer without uing a double pointer ?

I don't see why you can't.

> because the vector just store a copy of the pointer

Yes, but you don't care about this. Think about how you would free the resource.

delete p;

Let me ask you this. What matters here? The value of p, or whether p was the original pointer or a copy? Let me put it another way, is this invalid:

int * a = new int;
int * b = a;
delete b;

Do you think that is invalid? If no, then you think a copy is fine. Which is inconsistent with your argument. If you say it is invalid, then you believe the argument to the delete operator is the original variable, which is quite wrong.

Quote

Only if you discard the pointer itself. If you copy it around, you still have that value.