diff options
author | Orgad Shaneh <orgad.shaneh@audiocodes.com> | 2016-05-15 14:53:38 +0300 |
---|---|---|
committer | Orgad Shaneh <orgads@gmail.com> | 2016-05-29 18:47:56 +0000 |
commit | 261f9101dd8b03019251cf9aa58382de0fbde2e7 (patch) | |
tree | 97ce708ffed5f679d64b6d567639ab6b14414065 /src/plugins/platforms/minimal/minimal.pro | |
parent | 0f559a2d998d7ff5b7dec83a1c7e8a9996cbaa26 (diff) |
QLockFile: Use a more robust stale file detection
When a process that locked a lockfile crashes on Windows, sometimes
a new instance of the process fails to lock.
Unfortunately, I can't find a way to reproduce the problem consistently,
but it happens from time to time with Qt Creator and Qbs.
There are several ways to detect a dead process on Windows. Some of
them can be found in stackoverflow[1].
The current implementation of stale lock detection is based on the
second answer (using WaitForSingleObject), but apparently it doesn't
work in 100% of the cases.
The most voted answer[2] (using GetProcessExitCode) proves to work also
on this case.
[1] http://stackoverflow.com/q/1591342/764870
[2] http://stackoverflow.com/a/1591379/764870
Task-number: QTBUG-53392
Change-Id: Ied7bf00985d0f12e833b887a0143f7bdeee3e772
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Diffstat (limited to 'src/plugins/platforms/minimal/minimal.pro')
0 files changed, 0 insertions, 0 deletions