PANIC event line full on Gigabeat F40

[captain_cornflake]

OK, apologies if this is a bit waffly, but I when I'm debugging problems I always find too much detail is better than not enough...

I've been getting the occasional PANIC messages for the last few weeks, over various (official) builds.  Until today, they've always followed the same (largely unhelpful pattern).

I've got a root playlist (ie. of every track), which I've been playing on random, and doing a fair bit of skipping the odd track, when an artist I like comes on, I might add another of their tracks to the playlist etc. nothing special.  Every now and again the player hung for about 5-10 seconds, I just had time to glance the "PANIC" line at the top before the player shutdown, and needed the battery switch to be turned off/on before it would reboot.  It would normally be fine for w few days and something similar would happen.

Thinking it might be a disk problem, I ran a scandisk, but it found no problems.

Today I had something similar happen (but not quite the same) and I finally managed to catch the rest of the message.  This however wasn't in the middle of playing a track.  I was playing the root playlist, and just added an additional track by µ-Ziq, and then immediatley after returning to the WPS accidentally skipped 2 tracks.  I pressed left twice to skip back, and at that point the system hung and displayed "PANIC event line full".  Unlike previosuly this didn;t shut itself down, and was unresponsive.
I toggled the battery switch and rebooted, then selected the "continue plaback" option.  I immediately got the same error.
I once again toggled the battery switch, restarted, and manually selected a track to play rather than continuing.  It now seems fine again (for now)

Does anyone have any idea what is causing this?
I tried searching, but only found this.

I'm going to try completely removing rockbox and re-installling as that seemed to work for lestat...

Oh forgot to mention, current rockbox version is r17452M-080511 (but as I say has also occurred on other recent builds).  I've also attached a copy of the config

[MarcGuay]

current rockbox version is r17452M-080511

The "M" stands for modified.  Where'd you down the build from?

[captain_cornflake]

That's strange...
I have used modified builds in the past (most recently one I compiled with album art, before it was part of the standard build).

Recently though it's been 100% genuine rockbox from the current build option on the main menu...

I think a fresh install is definitely the way to go

[Llorean]

Well the version number won't be fixed by a fresh install. But every now and then a build server produced a build with an "M". It's not really modified in that case, it just means our system for not including the M isn't quite perfect yet, and so we have to double check about the version number when we see someone include it.

[captain_cornflake]

Well I've cleared the whol lot out and re-installed (No M on the version this time!).
I tried to recreate the problem as it happened earlier today, and it didn't error this time.

I suppose the only way to tell if it fixed it is to give it time and see if it recurs...

[captain_cornflake]

One week on, and no problems.
I've got no idea what the cause was, but it appears a fresh installation sorted it.