Our RCP application logs a fair bit, but only INFO and above are output to console. On windows/linux this is ok, but on OSX all logging seems to be passed to syslogd, which then decides what to log and not log, this means handling thousands and thousands of FINEST log messages, this makes syslogd use 140% cpu and gobble up memory. After running our app for about 3 minutes syslogd uses 2.5gb of memory and the whole system becomes unusable. Killing syslogd/rebooting is the only cure. Starting the app from console makes it log directly to console, and there is no problem.
How can I stop syslogd handling my RCP logging on OSX?
Take a look at your RCP Application’s RCP.App/Contents/Info.plist file. The default file generated by the RCP product build has <string>-consoleLog<string>.
This may be why everything ends up in syslogd.