10.5: Fix a potential cause of Core Image crashes

Nov 19, '07 07:30:01AM

Contributed by: Anonymous

After upgrading to 10.5, I discovered that a whole bunch of stuff involving Quartz CoreImage and Composer was broken. As an example, here's some, but not all, of what I saw:

You might get console messages like this:
11/5/07 2:32:55 PM Quartz Composer Visualizer[227] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[FILTER_NAME_HERE load:]: unrecognized selector sent to instance 0x15195000'
Well apparently the interface to ImageUnits has changed in some way, because it turns out that the problem was that I had a bad ImageUnit plug-in in /Library/Graphics/Image Units, installed from before (it worked in Tiger).

So, if you have any of the above symptoms, you may want to try removing anything suspicious from that directory. Note that the name from the error message is not necessarily the same name as the file. I'm a little surprised that Apple has not systematically wrapped the loaders for such plug-ins with exception handlers, so at least bad ones do not cause crashes.

Comments (0)


Mac OS X Hints
http://hints.macworld.com/article.php?story=20071105121422689