what does this error mean?

rekloos · Post by **rekloos** » Thu Jun 17, 2010 3:48 pm

"Memory corrupt: Size mismatch upon deallocation"

had this happen a few times....didn't pay much attention to it but now i wonder.
i'm on a mbp w/10.6.3 running Live 8.1.3

Sarrova-Q · Post by **Sarrova-Q** » Thu Jun 17, 2010 4:11 pm

+1 each time I got this error, Live did a "serious-problem-crash" instead of a 'normal' crash.
Would like to know as well.

Jorge3 · Post by **Jorge3** » Thu Jul 22, 2010 10:47 am

I may have a related problem. After a few seconds I opened Live 8.1.4, it almost always crashes, giving this message:

Memory corruption detected (0x5e)

It doesn't happen with the previous versions I have.

Another similar issue is discussed here:
http://forum.ableton.com/viewtopic.php?f=2&t=141584

slirak · Post by **slirak** » Thu Jul 22, 2010 12:13 pm

With some programming languages, you must explicitly say "I'm now gonna borrow this particular piece of memory" (allocation), and then, when it's not needed anymore, it must be explicitly returned as in "I'm not gonna use that certain piece anymore, be my guest, let someone else have it" (deallocation).

The error message basically says that some programmer didn't quite return what was borrowed. Sort of.

Do a bug report from within Live, that'll give the developers a good chance to fix it.

rekloos · Post by **rekloos** » Thu Jul 22, 2010 4:11 pm

thx for the breakdown slirak - jus wondering if it was hardware related.....

slirak · Post by **slirak** » Thu Jul 22, 2010 4:40 pm

rekloos wrote:thx for the breakdown slirak - jus wondering if it was hardware related.....

It's not, just a software bug. Mistakes in memory handling is a really common source of crashes in computer programs.

Error messages like these really shouldn't be displayed to end users, they're only meaningful to the developers. Barely to them either actually, too little info. That's why you should always attach the error logs to your bug reports, without them it's really difficult to guess where things went wrong. (The new Report a bug feature does all that for you. Nifty.)

ztones · Post by **ztones** » Thu Jul 29, 2010 5:11 pm

Has anobody found a fix for the Memory corruption detected (0x5e) error?

what does this error mean?

what does this error mean?

Re: what does this error mean?

Re: what does this error mean?

Re: what does this error mean?

Re: what does this error mean?

Re: what does this error mean?

Re: what does this error mean?