Bug 15353 - ImageViewer crashes fab4 (or any SP) if using a large folder structure as source
: ImageViewer crashes fab4 (or any SP) if using a large folder structure as source
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: Screensavers
: 7.5.x
: PC Other
: P1 major (vote)
: 7.5.0
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-21 05:55 UTC by Michael Herger
Modified: 2010-04-08 17:25 UTC (History)
0 users

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Herger 2009-12-21 05:55:29 UTC
I attached my external HD with my music collection (about 15k tracks in hundreds Artist/Album sub folders), started the image viewer set up to read from my "card". This defaults to /media/ - which in my case is the music collection with hundreds of sub-folders. As soon as I try to enter ImageViewer settings, it locks up for a few seconds while scanning the disk for images, then reboots.

This is not while displaying images, but when I tried to enter the IV's settings menu. Looking at the memory free decreased, while buffers increased. Free was close to 0 when the device crashed:

Mem: 122784K used, 3024K free, 0K shrd, 52364K buff, 13884K cached
CPU:   8% usr  46% sys   0% nic   0% idle  32% io   6% irq   6% sirq
Load average: 1.31 0.60 0.25 3/79 896
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
  751     1 root     R    44220  35%  26% /usr/bin/jive 
  787   751 root     S     7060   6%   5% jive_alsa -d plughw:2,0 -b 20000 -p 2 -s 16 -f 2
Comment 1 Michael Herger 2009-12-21 07:20:31 UTC
This is a potential crasher. It needs to be fixed.
Comment 2 SVN Bot 2009-12-21 07:21:28 UTC
 == Auto-comment from SVN commit #8238 to the jive repo by michael ==
 == https://svn.slimdevices.com/jive?view=revision&revision=8238 ==

Fixed Bug: 15353
Description: don't use recursion to scan our media folder for images. It seems to be too expensive.
Comment 3 Chris Owens 2010-04-08 17:25:20 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!