ghost version_XXX file false alarm (was: KDevelop 5.3.3 released)

[René J. V. Bertin]

Hi,

> René J.V. Bertin wrote:
> 
> As it turns out I have run into an annoying and elusive issue:
> 
> https://bugs.kde.org/show_bug.cgi?id=410103

Turns out this was a false alarm. It spent the afternoon trying to understand 
why KDevelop would be writing out 2 version_XXX in the kdevduchain cache and 
then this morning I finally had the idea to check who was using 
libKDevPlatformSerialisation.

Sure enough I had a not-so-zombie KDevelop 5.3.2 process running which I thought 
I had quit before logging off (the 1st time after upgrading to 5.60.0). My 
issues started after logging in. I tried to attach a debugger to understand why 
this "ghost" was still doing things but couldn't get a usable backtrace.

Two things would probably have helped me think of this sooner:
- using the hex version number in the version file, so I'd have seen an 
unexpected version_5030201 file.
- storing the application PID in the file instead of keeping it empty.

It's been a (potentially) interesting "experiment" though that has shown that 
the session can survive unexpected "failed to open registry" errors, i.e. that 
an immediate abort isn't required.

R.