Apparently, SDL on OSX does employ Objective-C. That means, at the very least, you'll need to wrap all of your SDL code with an NSAutoreleasePool. Now, depending on how much Objective-C is being used, you'll need to release the pool every so often, otherwise, you'll tie up a huge chunk of memory for unreleased objects.
Perhaps you'd like to try it along with Public.ObjectiveC, which should at the very least, give you an easy mechanism for freeing the pool from within Pike code.
Bill
On Sun, 29 Jul 2007, Johan Sundström (Achtung Liebe!) @ Pike (-) developers forum wrote:
That's anyone's guess, but that's the impression I got from the tip page. Lots of people seem to have run into this error with SDL, and that was the only page I came up with that offered anything remotely looking like a solution.