This is a small but important one.
Running more than one instance of Kombiner at the same time could silently corrupt your library database. It didn’t happen often, and most people would never know it was possible — but when it did, the results ranged from missing metadata to a library that wouldn’t open at all.
0.1.13 makes this impossible.
What Changed
Single Instance Enforcement
Kombiner now detects if another instance is already running on your machine. If one is, the second window won’t open — instead, the existing instance is brought to the foreground.
There’s no data at risk, no prompt to dismiss, no recovery steps. It just works the way you’d expect a desktop app to work.
Why This Mattered
Kombiner’s library is backed by a local database. That database is designed to be accessed by one process at a time. When two instances ran simultaneously — which could happen after a crash, through a launcher, or simply by opening the app twice — both processes would write to the same file concurrently. The result was undefined behavior: sometimes nothing, sometimes subtle data loss, sometimes a corrupted database that required manual recovery.
No action needed on your end. Update is available now through the app.
— The Kombiner Team