Mac Error - 111 (WhichZone failed (applied to free block))

This error sometimes occurs when you try to edit an existing title in the title tool.  You click in the title window, and get this error.  You try to close the title, and you get this error.  You're stuck.

This error is also yet another shining example of how terribly unintelligible Avid's errors are.  No one, and I mean literally no one, should ever be expected to memorize the error codes of the platform they're working on.  Period.  Put in a goddamn error handler and add some strings from the Programmer-Speak to Actual Normal Fucking English dictionary.

If you were to consult such a dictionary, you'd know that any time computers are talking about "free blocks" they're actually talking about RAM, or the type of hardware memory that computers use to run active applications.

Any time something having to do with memory fails, you're about to crash.

Case and point, what happens when you click "OK" in the error above?
Yup.

System errors are bad news.

So how did we get here?  What is going on behind the scenes that caused this?  Well, in case you never played the 100% memory game, Avid has some major memory leaks, causing seemingly innocuous tasks to fill up available RAM like freaking crazy, and eventually the memory will be so full that you can't do anything... open a bin, close a bin, play a sequence, save anything, or even quit.  This title bug occurs somewhere in the 90-ish percents, where Avid has enough memory to open the title editor, but just can't bring itself to actually acknowledge that said editor is open and to let you mess around in it.

There's only minor good news here:  you can click behind the effect editor and save your bins in the background before Avid bites the big one.

Once you've saved everything, force quit Avid, and if you haven't kernel panicked yet, disconnect from ISIS or UNITY.  If that doesn't cause you to kernel panic, go ahead and restart the computer.  There you go:  A kernel panic.

Pretty sweet, Avid's Horrible Memory Leaks.  Pretty freaking sweet.

Comments

Post a Comment

Popular posts from this blog

How to Reset your PRAM and Delete your Site Settings

After two years, it has occurred to me that I have been remiss in my duties.  Up until now I've failed to mention the most basic troubleshooting techniques for dealing with Avid:  Resetting your PRAM and Deleting your Site Settings.  Seriously, what's wrong with my brain? Basically whenever you're getting weird errors, or multiple bus thread error crashes in a row, or "you can't write to drive X" message when pretty fucking clearly you have write permissions, the problem isn't you; it's Avid.  That's a shocker, I know, and wholly unexpected, but the fact of the matter is that Avid is the only program I've ever used that required regular resetting of your Mac's PRAM (Parameter Random Access Memory).  Avid is also one of the rare pieces of software that corrupts it's own fucking settings.  Seriously, how is that even possible, Avid?  you generate  the settings on launch, so can't you do a goddamn checksum to make sure the existing o...
Read more

CM_LABEL_NOT_FOUND: tt:3, lnum:3

Image
Well this was a fucked up error. The actual message was:   Timecode not found for clip, 'CLIPNAME' and when you click MORE, you get  CM_LABEL_NOT_FOUND:  tt:3, lnum:3 , which was supposed to convey some sort of information. The internet was no use, because it apparently only cares about CM_LABEL_NOT_FOUND:  tty:3, lnum: 4 , which is something completely fucking different. Let me back up:  I got this error by trying to multigroup some clips.  The group was properly constructed and everything, all subbed out, all the AuxTCs were in place and correct.  Error. So... what doesn't have timecode?  Well, all the tapes were totally normal.  The iso audio was a bitch to deal with because my sound guy doesn't understand how to make polyphonic .WAV files.. let's start there. Okay, so we imported the sound files using Avid's autodetect polyphonic wave groups feature, and it worked, but all three iso clips that resulted had bas...
Read more

File 'Avid_MediaFiles' not found.

Image
This is a great error.  It's great for a couple of reasons.  Firstly, the problem isn't that "Avid_MediaFiles' can't be found.  That's the folder on your media drive named "Avid Media Files" and it's pretty goddamn easily found by both you and Avid.  No, the real problem is that a file *inside* Avid Media Files can't be found.  Which file?  Good question.  A database file.  What this error message should really say is: File 'msmFMID.pmr' not found. OR File 'msmMMOB.mdb' not found. Or the error message could be actually helpful and say: The File 'msmFMID.pmr' which should be in path 'MediaDriveA/Avid Media Files/MXF/Ingest1' cannot be found. You know, something actually fucking helpful.  But no.  No, this message basically just says that Avid lost something, it isn't sure what, and it sure as shit isn't going to let you save any bins until you fix the problem.  Also, opening the Med...
Read more