Bug 15617 - Switching from touch to remote skin killed Squeezebox Server
: Switching from touch to remote skin killed Squeezebox Server
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: OS
: 7.5.0
: Macintosh Debian Linux
: P1 normal (vote)
: 7.5.0
Assigned To: Alan Young
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-05 00:08 UTC by Michael Herger
Modified: 2010-04-08 17:26 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments
/var/log/messages from around OOM situation (12.29 KB, text/plain)
2010-02-05 00:09 UTC, Michael Herger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Herger 2010-02-05 00:08:06 UTC
Firmware 8453

While I as watching some pictures from Facebook, fab4 run out of memory, thus killed SBS. jive memory usage was pretty high:

Mem: 94564K used, 31244K free, 0K shrd, 680K buff, 12700K cached
CPU:  17% usr   3% sys   0% nic  79% idle   0% io   0% irq   0% sirq
Load average: 0.56 0.72 0.53 2/83 10285
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
  758     1 root     R    75200  60%  13% /usr/bin/jive 
  794   758 root     S     6980   6%   3% jive_alsa -d default -c default -b 20000 -p 2 -s 24 -f 1 
  793   758 root     S     7060   6%   2% jive_alsa -d plughw:2,0 -b 20000 -p 2 -s 16 -f 2 
    9     2 root     SW<      0   0%   2% [sirq-tasklet/0]
10280  9099 root     R     2692   2%   0% top 
 9097   672 root     S     2384   2%   0% dropbear -i 
   49     2 root     SW<      0   0%   0% [IRQ-34]
  649     1 root     S     2688   2%   0% /sbin/syslogd -S 
  116     2 root     SW<      0   0%   0% [IRQ-10]
    5     2 root     SW<      0   0%   0% [sirq-timer/0]
  682     2 root     SW<      0   0%   0% [wlan_main_servi]
  357     2 root     SW<      0   0%   0% [IRQ-7]
  681     2 root     SW<      0   0%   0% [ksdiorqd]
10204     1 root     S N  10048   8%   0% /usr/bin/perl /usr/squeezecenter/gdresized.pl 
10217     1 root     S <   6072   5%   0% /usr/sbin/smbd 
10218 10217 root     S <   6072   5%   0% /usr/sbin/smbd 
10216     1 root     S <   4140   3%   0% /usr/sbin/nmbd 
  672     1 root     S     2768   2%   0% /usr/sbin/inetd 
 9099  9097 root     S     2692   2%   0% -sh 

 We need some way to improve handling of oom events. Eg. first kill Samba, gdresized, the ImageViewer applet, before killing SBS? Or at least tell the user that SBS has been killed.
Comment 1 Michael Herger 2010-02-05 00:09:28 UTC
Created attachment 6491 [details]
/var/log/messages from around OOM situation
Comment 2 Michael Herger 2010-02-05 00:34:24 UTC
watching the ImageViewer a bit closer I couldn't find an immediate and important memory usage increase. But when I switched from using the touch interface to using the remote control was when memory usage increased by 10-15MB.
Comment 3 Chris Owens 2010-02-08 09:23:51 UTC
Alan notes that this is a memory issue.  Additionally, since logging is turned on right now, the Touch firmware is using more RAM than it will.
Comment 4 Alan Young 2010-02-09 05:08:23 UTC
Memory segment sizes on a 53MB jive, as identified by smaps:
rwxp                              [heap]  27336 kb 52%  52%
rw-p                                   0   6376 kb 12%  65%
rw-p                                   0   4456 kb  8%  73%
rw-s                       /SYSV0000de01   3532 kb  6%  80%
r-xp                       /usr/bin/jive   1328 kb  2%  83%
r-xp                    /lib/libc-2.8.so   1140 kb  2%  85%
rw-s                            /dev/fb0   1020 kb  1%  87%
---p                                   0    892 kb  1%  89%
rw-p                                   0    868 kb  1%  90%
Comment 5 SVN Bot 2010-02-12 10:58:23 UTC
 == Auto-comment from SVN commit #8498 to the  repo by bklaas ==
 == https://svn.slimdevices.com/?view=revision&revision=8498 ==

Fixed Bug: 15617
Description: Alan's patch to C code to optimize skin switching utilizing LRU cache for images
I've tested this on desktop all day and the speed of skin switching is greatly improved. No regressions detected in testing.
Comment 6 Chris Owens 2010-04-08 17:26:35 UTC
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!