This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#7253 - Dircache goes crazy
Attached to Project:
Rockbox
Opened by Kévin Ferrare (TiMiD) - Saturday, 02 June 2007, 16:46 GMT+2
Last edited by Kévin Ferrare (TiMiD) - Friday, 06 February 2009, 01:17 GMT+2
Opened by Kévin Ferrare (TiMiD) - Saturday, 02 June 2007, 16:46 GMT+2
Last edited by Kévin Ferrare (TiMiD) - Friday, 06 February 2009, 01:17 GMT+2
|
DetailsHi,
I've got a strange behaviour with dircache : one reboot on 2 dircache is enabled, and the other one it isn't. 1 time on 2 (when dircache will be enabled for this session) I get the message "scanning disk ..." at boot time. I don't know if I'm clear, here is what I get : while(true){ Power on "scanning disk ..." I can use direcache Power off Power on No message and dircache is not activated (it is in the options, but disk spins in file browser) Power off } I've tried reseting the settings, changed nothing. I don't really get what's going on. I'm using the today's build (2007/06/02) but I've got this problem since ... well maybe 2 or 3month after an update, I don't remember exactly. I don't think it's related to bug #6735 because it's easily repeatable and doesn't depends of the font used. Am I the only one to get this behavior ? |
This task depends upon
Closed by Kévin Ferrare (TiMiD)
Friday, 06 February 2009, 01:17 GMT+2
Reason for closing: Out of Date
Additional comments about closing: I could be wrong but it seems to be working now
Friday, 06 February 2009, 01:17 GMT+2
Reason for closing: Out of Date
Additional comments about closing: I could be wrong but it seems to be working now
USB is not involved at all.
If I let the player run for awhile before shutting down, this doesn't happen. So perhaps it's a result of shutting down while the audio is still being buffered?
Whenever I check the dircache status, it's active, and size is well below it's limit (about 1MB, 13829 entries).
I am starting with a completed build of the dircache, and assuming that the fact that a scan had completed would mean that no further foreground scan was needed, but if I shut down during a background scan, it then triggers another foreground scan on the next boot.