tbh I was a bit sceptical about that previous patch anyways. If I read it correctly, it only tried to not leave stale lock files in some circumstances. Problem with our case is that it might happen while the app is suspended and then OOM killed which means there is no chance for the Qt code to clean it up and it will leave a stale lock file, no matter how clever it tries to be in cleaning them up.
What I think needs to happen is that when the app starts up again (or tries to obtain a lock) it needs to be clever enough to determine that this lock is a stale one from a previous and ignore it.
tbh I was a bit sceptical about that previous patch anyways. If I read it correctly, it only tried to not leave stale lock files in some circumstances. Problem with our case is that it might happen while the app is suspended and then OOM killed which means there is no chance for the Qt code to clean it up and it will leave a stale lock file, no matter how clever it tries to be in cleaning them up.
What I think needs to happen is that when the app starts up again (or tries to obtain a lock) it needs to be clever enough to determine that this lock is a stale one from a previous and ignore it.