Hi all,
I just had my MB's UI completely lock-up on me again last night. The mouse would move, but *nothing* would respond to clicks. I could close the lid and it would sleep, but when it woke, it was still non-responsive. It was as though the Core Image was hosed, and here's my theory:
Last night, I was using Image Tricks to crop some photos. When I pressed the Apply button for the crop, that's when it locked up. Image Tricks uses Core Image from what I understand.
I have some other utility (can't remember the name and I'm at work) which creates photo droplets, which I use to resize images for posting to the web. Well, sometimes the droplet is extremely slow or doesn't respond at all, and I believe it's using Core Image to do the image manipulation.
If I reboot, both of these programs work fine. I just seems that after several invocations of either, things start going wonky as described. It's not a gigantic deal, although the complete lock-up last night required me to hold the power switch and kill the system. It's as though Core Image or something related doesn't cleanly exit and eventually leaks or becomes overloaded after multiple uses.
Has anyone else seen this behavior related to Core Image (or whatever, if my theory is not correct)? Obviously, it's hard for me to collect any debug info when things are completely locked-up, so I figured I'd get opinions before I worried about investigating it further.
Mike
I just had my MB's UI completely lock-up on me again last night. The mouse would move, but *nothing* would respond to clicks. I could close the lid and it would sleep, but when it woke, it was still non-responsive. It was as though the Core Image was hosed, and here's my theory:
Last night, I was using Image Tricks to crop some photos. When I pressed the Apply button for the crop, that's when it locked up. Image Tricks uses Core Image from what I understand.
I have some other utility (can't remember the name and I'm at work) which creates photo droplets, which I use to resize images for posting to the web. Well, sometimes the droplet is extremely slow or doesn't respond at all, and I believe it's using Core Image to do the image manipulation.
If I reboot, both of these programs work fine. I just seems that after several invocations of either, things start going wonky as described. It's not a gigantic deal, although the complete lock-up last night required me to hold the power switch and kill the system. It's as though Core Image or something related doesn't cleanly exit and eventually leaks or becomes overloaded after multiple uses.
Has anyone else seen this behavior related to Core Image (or whatever, if my theory is not correct)? Obviously, it's hard for me to collect any debug info when things are completely locked-up, so I figured I'd get opinions before I worried about investigating it further.
Mike