oh ok, that will do it (re: changes in disk write implementation)
@Justmat i think you were following the PRs on the disk worker threads, but it was a pretty complex change so i’d certainly any feedback or reports of weirdness
reason i ask here is, Sam is just the kind of thing that would be affected / can push the envelope of the write-to-disk feature.
before changes, disk-write was executed immediately and would stall event handling in crone. it would also take super long to write (minutes, for the whole buffer) so the hang could be long and look like a crash.
after changes, you should be able to queue up a practically unbounded number of disk-write “jobs” that execute in the background, much more quickly. (~few seconds for whole buffer)
if we need to, we can pretty easily add a completion callback mechanism.
