Ableton Forum

When I open up a live set, I get "syslogd" process using 100+% CPU. I've sent of a support email to Abes but just had a similar experience using Kore standalone.

Console gives a log report which is basically this, repeated hundreds of times:

20031/08/2009 11:33:11 PM [0x0-0x72072].com.native-instruments.Kore Player[806] *** set a breakpoint in malloc_error_break to debug
31/08/2009 11:33:11 PM [0x0-0x72072].com.native-instruments.Kore Player[806] Kore Player(806,0x1b08fa0) malloc: *** error for object 0xa97e20: Non-aligned pointer being freed (2)
31/08/2009 11:33:11 PM [0x0-0x72072].com.native-instruments.Kore Player[806] *** set a breakpoint in malloc_error_break to debug
31/08/2009 11:33:11 PM [0x0-0x72072].com.native-instruments.Kore Player[806] Kore Player(806,0x1b08fa0) malloc: *** error for object 0xa97e20: Non-aligned pointer being freed (2)


Opening a Live project gives a similar log but with, of course, NI Kore repalced with Ableton. It all results in massive CPU and fan use which then dies down,

Any ideas? Live 7.0.16, MOTU Ultralite, OS X 10.5.4 (but was the same with 10.5.7.

Cheers

dazzer wrote:31/08/2009 11:33:11 PM [0x0-0x72072].com

That's clearly your problem right there. Duh.

In the string here:

806,0x1b08fa0) malloc

you need to change the 6 to a 7, and any x's to y's.

I dunno whether to laugh or cry at those replies.

Googling shows that loads of people have spontaneous "syslogd" errors but all of them are different and none of the suggested solutions have worked so far,

Sniff.

com.native-instruments.Kore Playe <---- probably a good clue on where to begin

I had a similar problem last year with the AU version of BFD2 not playing well with Live. Simply using the VST version fixed things for me. Some plugins/versions/configurations/drivers or any wacky combination thereof can fubar things real quick.

sublimelobc wrote:com.native-instruments.Kore Playe <---- probably a good clue on where to begin

Yep, sounds like Kore Player is dying and taking things with it. Syslogd is basically a program that sits in the background and logs events and errors in the OS. Try updating to the latest Kore Player (or an older version if the problem started after upgrading) and see what happens. HTH

Cheers for the replies.

The"syslogd" with all the NI stuff does indeed point the finger at Kore but when I open Live the syslogd doesn't mention Kore specifically, just mentions Ableton about a million times so I'm not sure if the problem is just Kore or Kore plus Live.

As for VST v AU, Kore gives me a massive sylog entry when I open it up standalone, so I'm not sure about that. I'll see if there's a later version of Kore available

If anyone has anything else to add please feel free, even if it's Tarekith or beats me with more comedy pearls...

For those of you following the thread with interest, here's a miniscule extract for the the Live syslog entry

31/08/2009 7:38:07 PM [0x0-0x4a04a].com.ableton.live[608] Live(608,0x2352fa0) malloc: *** error for object 0x27e61270: Non-aligned pointer being freed (2)
31/08/2009 7:38:07 PM [0x0-0x4a04a].com.ableton.live[608] *** set a breakpoint in malloc_error_break to debug
31/08/2009 7:38:07 PM [0x0-0x4a04a].com.ableton.live[608] Live(608,0x2352fa0) malloc: *** error for object 0x27e61270: Non-aligned pointer being freed (2)


"non-aligned pointer being freed" is my favourite bit.

If anyone wants the full 267 page doc, just PM me.

it just works

your syslogd database has become corrupt.

use lanchctl to stop it and then delete the database (which can grow quite large, it will be recreated on startup). Use these terminal commands:

sudo launchctl stop com.apple.syslogd
sudo rm /var/log/asl.db

You can restart syslogd:

sudo launchctl start com.apple.syslogd

@ djsynchro -my response to you is "IRQ conflict"

@ gomi - cheers, already tried that (been Googling "syslogd" for days) but it didn't work.

Further development via chat with Abes support, If I delete Kore Player from tracks, the syslog problem disappears.

BUT

In tracks that have Rob Papen's SubBoomBass, the syslog problem is replcaced by a Synsopos (Syncosoft) process which does exactly the same thing, CPU well over 100%.

I'm looking forward to a reply from support saying "well, don't use Syncrosoft licensed synths or Kore and you'll be fine".

I can tell you, I'll have a good giggle if they send me that as a reply.

just disable syslogd