Trying to Free Object On Heap As Array Throwing Debug Asserts

[HyperShadow]

If some code throws a _IsCrtValidPointer or some error along those lines using the debug versions of Free() will that be a problem in the Release versions? Memory Corruption/Leak?

Ex:

Class Foo
{
}

Foo *a[2];

a[1] = new Foo;

delete [] a[1];  <-- Throws the Assert mentioned above 
// Code above should be delete a[1];

In debug this throws an assertion, but under Release it runs fine.. what I'm wondering is does the Release version leak or corrupt memory in anyway?

[Daved]

It is undefined behavior. It could cause a crash (even if it works this one time). It could corrupt memory and the crash or incorrect output won't occur until later in the program.

There's no reason to use delete [] there instead of delete.

[HyperShadow]

There's no reason to use delete [] there instead of delete.

Yep, I have changed it, but it was something that at the time was a typo/mis-overlooked piece of code and lasted for a long time... Just wondered if it was possibly corrupting the heap the whole time it was like that or if the debug versions of the heap were over-causius (crap my spelling in the toilet tonight) throwing an ASSERT... your answer quenched my thirst for knowledge:

It is undefined behavior. It could cause a crash (even if it works this one time). It could corrupt memory and the crash or incorrect output won't occur until later in the program.

Thanks for the fast reply!