DavidGZ

Just in case something breaks, this is the commit where the code for sending that message was added: eb75a10ac9236c3651ee71bc0941a7e97c335a14

> One can easily change this behaviour with as little as adding a few debug outputs. Here do you mean that it crashes but sometimes if you add some debug...

> Exactly. I had to be very careful not to "scare away" ;-) the crash and its exact location (because yes, you have guessed it, the place where it crashes...

I'm almost sure that the behavior explained above was present before this commit 09d68c1c7fb659683485ebde820f6ff1f064cd56, but I can't trust my memory 100% ;-). But because this fix touches code related with...

Hi, Why didn't you upgrade to a more recent version (1.19)? If there is no particular reason, could you please try with a 1.19 snapshot? https://freemint.github.io/#snapshots

> > 1.18 is the latest version on github.com! But I can certainly try a snapshot from github.io. Yes, you're right sorry, a release should have been done for the...

I've been looking into this, this is what I've found out: - Only happens when copying/deleting from a FAT partition, ext2 doesn't have the problem. - If the operation is...

> The FAT file system driver locks a cache block every time you enter a new directory level depth [1], it's the cache block with the FAT cluster for that...

> I guess that can only be solved by rewriting the cache management to not use a fixed cache block size. Using 64k for a cache block when you only...

> > What is relationship of this to `FS_CACHE_PERCENTAGE` ? Couldn't this be somehow used for the same purpose? > Nice!, the code is already there :-) I'd like to...