I switched to “CURLHandle”—an extremely painless experience. CURLHandle replaces NSURLHandle without your needing to do a single thing to your code. But CURLHandle leaks memory too. It leaks a lot less: a CFMachPort, CFRunLoopSource and two CFBags. I was able to remedy the problem by only creating a CURLHandle when you change the image URL, which won't be too often.

I am now out of stuff OmniObjectAlloc can help me with: the continuing leaks don't register. Yet I'm still leaking 50K per image load! I commented out the image drawing, then the image loading, then the status window notification, so about all the app does is load a URL on a timer, and it still leaks.

So, DockCam is on hold until I resolve this last remaining issue. I've fixed the rest of the bugs, and some more I discovered along the way. Right now I'm trying out MallocDebug.

Subpixel rendering in Jaguar. Perhaps my eyesight's too good or something? I can see the color fringes when looking at the screenshot on my TiBook. While it's obviously smoother, it is somewhat disconcerting.

Not sure I like the new Aqua theme very much. It's too glassy, which I guess is the point… but the popup menu arrows and the gigantic window sizing corner have to go.

(Note: Bill Bumgarner points out that these screenshots are in GIF format, so they've lost something in the conversion to a 256 color palette. To me, both Jaguar's font rendering and the revised Aqua theme look much better on my CRT at work than they do on the TiBook's LCD; go figure.)