Bugzilla – Bug 3659
Slimproto Backtraces Filling up Logs
Last modified: 2011-03-16 04:39:14 UTC
2006-06-28 14:58:05.8704 Backtrace: frame 0: Slim::Utils::Misc::assert (/usr/local/slimserver/Slim/Networking/Slimproto.pm line 399) frame 1: Slim::Networking::Slimproto::process_slimproto_frame (/usr/local/slimserver/Slim/Networking/Slimproto.pm line 256) frame 2: Slim::Networking::Slimproto::client_readable (/usr/local/slimserver/Slim/Networking/Select.pm line 141) frame 3: Slim::Networking::Select::select (/usr/local/slimserver/slimserver.pl line 702) frame 4: main::idle (/usr/local/slimserver/slimserver.pl line 638) frame 5: main::main (/usr/local/slimserver/slimserver.pl line 1276) Here's the problem. /usr/local/slimserver/Slim/Networking/Slimproto.pm, line 399: 389 } 390 # make sure volume is set, without changing temp setting 391 $client->volume($client->volume(), 392 defined($client->tempVolume())); 393 } 394 return; 395 } 396 397 my $client = $sock2client{$s}; 398 399 assert($client); 400 401 if (!defined($client)) { 402 msg("Client not found for slimproto\n"); 403 return; 404 } 405 406 if ($op eq 'IR ') { 407 # format for IR: 408 # [4] time since startup in ticks (1KHz) 409 # [1] code format
This indicates something missing on the client end. I'm seeing similar things in your other reports that can only be explained by some sort of problem getting info from the client. What do you have connected to slimserver at the time? What is displayed on the screen?
Using Softsqueeze 2.7 Only
What is softsqueeze doing at the time? 6.3 and softsqueeze is a combination I use at work all the time, and I can't recall the last time I saw debug backtraces as a result.
New softsqueeze seems to be having some difficulty talking with the server. Perhaps that's the problem? I didn't have this issue with 2.3, but the 2.7 version was included with 6.3.0, so I installed it.
It is possible, but still a difficult one. When a player connects, the server creates a $client. This $client will be removed if the player is detected as being gone for a period of time, 5 mins I think. ah...in fact, this has come up before in reference to softsqueeze. I'm going to mark this as a dupe of bug 3412. Richard should be already looking at this and the relevant ppl for this problem are already attached to that report, and you'll be added to the cc'list automatically and included on any further discussion there. Please add any new comments to that report. thanks. *** This bug has been marked as a duplicate of 3412 ***