by JohnJ9 » Thu Dec 27, 2012 1:12 am
I ran into this and figured it out. It started happening after an update I picked up a couple weeks ago. It turns out, the behavior is that realsched is reading an option for realplayer where it can monitor your library and watch for new arrivals. By default, there are a few directories set up to be monitored, and a default period of checking once a minute. realsched spawns an instance of realplayer that chugs through your specified directories full tilt boogie on one core, and will read until finished. On my system, it would read 12gb of data before finishing, then doing the same thing again in a minute. I turned the option off in the Libraries settings, and the problem went away. I couldn't find a posting that had the actual problem and solution anywhere using Google, so I thought I would post this here so that it could be tripped over should it happen again.
I ran into this and figured it out. It started happening after an update I picked up a couple weeks ago. It turns out, the behavior is that realsched is reading an option for realplayer where it can monitor your library and watch for new arrivals. By default, there are a few directories set up to be monitored, and a default period of checking once a minute. realsched spawns an instance of realplayer that chugs through your specified directories full tilt boogie on one core, and will read until finished. On my system, it would read 12gb of data before finishing, then doing the same thing again in a minute. I turned the option off in the Libraries settings, and the problem went away. I couldn't find a posting that had the actual problem and solution anywhere using Google, so I thought I would post this here so that it could be tripped over should it happen again.