I am not entirely sure whether this is a hardware issue, so depending on the background it might have to get moved to the database forum.
Anyway, I am using the most current build (35d69c8) on my Sansa e280v2, though I have encountered similar problems/symptoms with earlier versions, including 3.13 stable.
The problem is, when I enable the "Load to RAM" option in the database settings, then database browsing is greatly accelerated (as it should be), but the player can no longer play back music. Instead, when trying to play back music, with the current build I get a white screen with kernel panic. The stable build would simply do nothing, just show the playback screen but not play.
I have quite a lot of music on the player, as I use a 256GB card with about 22,000 files spread over 2,000 directories. Playback works fine again if I disable "Load to RAM", so I think it is a reasonable guess that my database takes up so much RAM that not enough is left for playback.
What is odd to me is that the same card and "Load to RAM" work fine in my Clip+. It was my layman's understanding that these two DAPs were quite similar internally. Do they differ in their amount of RAM? I could not find the amount in the e280v2. Or maybe the prettier big-colour-screen-GUI in the e280v2 also needs more memory, and in combination this takes too much for playback?
I am not really hoping for a solution to this, but I am curious and would like to know what is going on.