Hot reload during a save can delete assets the old load is committing #10
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A hot reload while a save, copy or move is running leaves the old load's code finishing it. Each load has its own
AssetStoreand its own store lock, so the old commit and the new load's clean-up don't exclude each other.Two ways that can lose assets:
Either way the item is written without assets it needs, and a move then deletes the cloud original.
Seen as a risk on 2026-10-07: 0.7.7 and 0.7.8 were hot-loaded while a 0.7.6 move was running. Neither sweep deleted anything (no "Deleted N asset store files" line), and the move had not committed yet.
Options
SemaphoreSlim