Yikes! I’ve never seen that before–how about you, Roger, did you ever come across that while developing OSX?
I assume pview still runs fine without reporting these error messages?
It certainly sounds like something’s out of sync between panda and direct. There might be a problem in the large elapsed time (days?) between when you checked out panda and when you checked out direct, if some low-level changes have been added in the interim–if you haven’t done this already, it might be a good idea to cvs update all three trees (dtool, panda, direct), and then make install all three trees again. Maybe make clean install for good measure.
Other things you can try: you can follow the suggested advice, and set MallocHelp to try to figure out who’s generating the errant free(); that might give us a clue. I know nothing about this MallocHelp thing; I guess that’s an OSX feature.
Also, does it only happen when you open a window? For instance, suppose you set “window-type none” in your Config.prc file–do you still get error messages like this when you start?
David