Actually, the word ‘causing’ conveys more certainty than I would like, but turning on the audio in Max 5 when a particular patch is open seems to consistently coincide with syslogd beginning to hog the CPU. The patch is quite complex and does use some 3rd party externals.
I realise that there are fairly widespread syslogd issues in leopard (google ‘syslogd leopard’, for more), but I had not noticed any problems with it until now. If some knowledgeable Mac user could explain how I might investigate this further, then I’d be very grateful. For instance, how can I find out what is logging all these error messages, and what the messages are? Ideally I could trace the problem to a particular object…
I’d use the application called Console (look in Applications/Utilities for it) and within that see what the messages are about. I remember having some crazy amount of messages being sent by my M-Audio drivers back when they weren’t Leopard compatible: they used some deprecated calls of some sort which in turn made syslogd report this like a madman (meaning probably hundreds per second).
My guess is that somewhere this 3rd party external of yours does something special of some sorts.