Bug 3507 - Rare: on XP, Slimserver uses all CPU and memory, then crashes after new SB is connected
: Rare: on XP, Slimserver uses all CPU and memory, then crashes after new SB is...
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Service
: 6.3.0
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-07 15:54 UTC by Chris Owens
Modified: 2008-09-15 14:38 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Owens 2006-06-07 15:54:12 UTC
I don't have solid repro instructions for this yet, but this is the 3rd or 4th time I've seen it, so I'm putting it in.

On XP, if I connect an additional or different SB3 than what I was originally using, sometimes the system will start to behave very slowly.  Checking the task manager shows that slim.exe is using all available CPU, and allocating a ton of memory.

After a while, XP will display a message that it's out of virtual memory, and some programs may have difficulty while it's increasing the amount of virtual memory available.  At the same time, the slimserver process (slim.exe) dies with the following message in the event viewer:  The following information is part of the event: Perl interpreter failed
Comment 1 Chris Owens 2006-06-16 13:35:58 UTC
Okay, I've been running 1-3 Squeezeboxes and Slimp3s attached to 6.3 for some time now, and I haven't seen this bug in a good while, so I'll go ahead and mark it 'works for me'.  If anyone sees this again in the future they can reopen it.
Comment 2 Andy Grundman 2006-06-20 05:33:28 UTC
Also see bug 3581 which was probably the real cause of this issue and easily reproducible.