Archives / Search ›

Mike Pinkerton (whose weblog I don't read regularly because it doesn't have a syndicated version I could find) complained about nobody at MacHack using Mozilla on their TiBooks. I find Mozilla barely usable on my dual G4/533 and G4/800 TiBook—to the point I use it as my primary Web browser, and have for months—but unusable on a G4/400. That might be part of it: not everyone can afford the latest hardware to run their Web browsers on.

Pink also complains that there aren't enough external Mozilla Mac developers. I've tried, on several occasions, to contribute; most often I just get ignored or yelled at that I shouldn't be doing something. While the few Mozilla/Netscape developers I know personally are quite nice (as were those I met at MacHack—there was a huge Netscape contingent there: scc, pink, smfr, brade, dagley, and another?), the whole development process seems amazingly cliquey and resistant to people who don't have their entire lives to give over to the greater good that is Mozilla. Scott Collins was bragging on #mozilla about his 23" Cinema HD display. Then as now... *drool*. I gotta get me out of school so I can afford this stuff again.

Which leads me back to work. I'll get back to DockCam next weekend if miscellaneous festivities don't overwhelm me.

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.