Awfully quiet around here…
Sorry about that! Usually I’m quiet when I’m working too hard. The good news is that I will be entering beta soon.
The first alpha testers received their copies a week ago, and the first lesson is that Find It! Keep It! doesn’t work on Intel Macs, even with Rosetta emulation. In the mean time, I’ve been busy writing documentation, building the website’s content, and fixing bugs and rough edges. There’s still a lot to do, but the end is in sight.
While I’m blogging, I want to mention this post by bbum. On Linux I used Valgrind. It was invaluable, and I would love to have it on Mac OS X. I’ve tried various Mac tools (OmniObjectMeter, ObjectAlloc) and while they’re pretty they slow Find It! Keep It! too much to be useable. As usual, with Apple, all along I had a tool called “leaks” on my harddrive… Would have been nice to know about it! Quoting bbum:
In a Terminal window….
setenv MallocStackLogging /path/to/foo.app/Contents/MacOS/foo
… you should see a diagnostic message like …
malloc[PID]: recording stacks using standard recorder
… then, in another Terminal window…
leaks PID
… do whatever it is in the app that you suspect causes leaks. The leaks process will print detailed information about the leak, including the backtrace of the appropriate thread within the application at the time the memory was allocated.
Bbum’s link doesn’t work right now, so this is the Google Cache, and the post he references is still on the Wayback machine.
It turns out the Webkit crew use it too