FS#12614 - Bug while seeking on Sansaclip+

Attached to Project: Rockbox
Opened by Alan (hawui1) - Tuesday, 13 March 2012, 19:58 GMT
Last edited by Frank Gevaerts (fg) - Tuesday, 13 March 2012, 20:18 GMT
Task Type Bugs
Category Database
Status Unconfirmed
Assigned To No-one
Operating System Sansa AMSv2
Severity Low
Priority Normal
Reported Version Release 3.10
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Hi, firstly i put Sansa c200 because SansaClip+ is not available in the list.
My player is a Sandisk SansaClip+ bought 6 months ago with an 8Gb class 4 Sandisk microsd (that is currently empty, no songs stored).

Steps to reproduce the issue (after a fresh installation of the Firmware, no settings changed):

1) Switch on
2) -> database
3) -> track
4) select any track
5) press the central button
6) Erase Dynamic Playlist? is displayed.. Select Yes
7) countdown then starts to play
8) Seek to the next song (it happens at the first seek or might need three, four one after the other)

Data abort
at 30813E44
FSR 0x8
(domani 0, fault 8)
address 0x62E90028

- I installed version 3.10 on top of version 3.09, but later on I tried to uninstall completely 3.10 and reinstall it from scratch and the issue is the same.

- After the crash i have to keep the "switchoff" button pressed for a while.. then I press it again to restart the player and I try to resume the song I get "playlist control file is invalid" or "nothing to resume"

- behavior is the same with or without the SD card

- The issue was randomly happening (but very very rarely) also on the previous version of the firmware (3.09) I got the error a couple of times in 6 months.
This task depends upon

Comment by Alan (hawui1) - Tuesday, 13 March 2012, 20:05 GMT
Note: if you select one Album and then you seek ahead or backward it seems that the issue doesn't show up.
Comment by MichaelGiacomelli (saratoga) - Tuesday, 13 March 2012, 20:58 GMT
Do you mean seek (as in seek through the track) or skip (as in go to next track)? Both seem to work for me in the current build on the Clip+.
Comment by Alan (hawui1) - Wednesday, 14 March 2012, 12:18 GMT
Yes, going to the next track..
one more detail.. on my SansaClip+ I have only .ogg files 192Kbps (since you changed the decoder maybe it makes a difference?)
Comment by Alan (hawui1) - Wednesday, 14 March 2012, 20:32 GMT
I tried other things.. one interesting result is that the critical stop happens ONLY if I select the database->Tracks and then i try to skip to the next track as explained above.. If I select Database->Album and then I skip forward or backward in the tracks of the same album everything seems to work perfectly
Comment by Alan (hawui1) - Saturday, 17 March 2012, 10:48 GMT
Did another test. I deleted all music files and placed only mp3.. doing the same operations described above doesn't reproduce the error. Tried also with WMA files, no problems when "torturing" the Clip+ moving forward/backward skipping from song to song.
There's an high probability the issues are in the .ogg decoder.
Comment by MichaelGiacomelli (saratoga) - Wednesday, 09 May 2012, 22:30 GMT
Yes it looks like its in the Vorbis decoder, that address is it's malloc free function. I guess on skipping something isn't cleaned up right. However, since 3.10 a lot of bugs in that code have been fixed. Can you try the current build and see if the problem can be reproduced?

Also, since memory allocation is very different for different vorbis files, can you upload two that cause it?