spawn a "production"/"detached" tracking job (ie one that isn't connected to the UI)
load another project, or create a new project in the same APT session (eg without closing the UI)
Step 3 will try to clear and reuse your cachedir and bad stuff will ensue as the production job is still read/writing to it.
One easy fix would be to always create a new cachedir whenever a project is loaded/created, even within a given/current session. Safer in general, but root cachedir bloat-rate may increase.
Step 3 will try to clear and reuse your cachedir and bad stuff will ensue as the production job is still read/writing to it.
One easy fix would be to always create a new cachedir whenever a project is loaded/created, even within a given/current session. Safer in general, but root cachedir bloat-rate may increase.