you allocated a block of memory, some 284 bytes in size, and then accessed something just beyond the end of the chunk that was given to you, at offset 292.
This snippet is likely to cause a similar error:
char* p = (char*) malloc(284);
p[292] = 0;
the problem will typically show when the memory manager checks the borders of your allocation, so if your code would like this:
CMyclass* pCMyclass = new CMyclass();
...
delete pCMyclass;
then the problem would occur when executing the delete statement, although the error could be anywhere in the CMyclass object.
————————————————————————————————————————————————————————————
you wrote past the end of the object somehow. The heap manager in debug mode puts sentinel['sentinəl] values before and after allocations and checks these when you deallocate the memory. If the sentinel values have changed, it means you've written into the memory you shouldn't have done.
http://www.codeproject.com