I'd guess it's a threading library issue--I wouldn't be surprised if my box and kernel don't support it the same way yours does (and since it's a Kuro Box I can't easily hack or update the kernel) and perl is forced to emulate it by creating a new process.
I haven't noticed the long delay on startup that you've mentioned. SlimServer takes about the same amount of time to start with our without your plugin (~20 seconds). The Threads->new returned message is almost immediately after the creating thread message. Perhaps this is related to the fact I've got three slimserver processes showing up. max.spicer Wrote: > That's strange. I'm not sure you should ever be able to see the thread > in th process listing. I only ever have one process running. This > could be down to different threading libraries, maybe? > > Have you noticed SlimServer hang when the plugin starts up (straight > after "NowPlaying: Creating worker thread" if you've got debug on)? It > does this for me sometimes, but not always. I'd love to know what's > going on! > > Max -- mrfantasy --Mike ------------------------------------------------------------------------ mrfantasy's Profile: http://forums.slimdevices.com/member.php?userid=1127 View this thread: http://forums.slimdevices.com/showthread.php?t=18597 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/plugins
