diff options
| author | Fuwn <[email protected]> | 2022-02-03 13:04:54 +0000 |
|---|---|---|
| committer | Fuwn <[email protected]> | 2022-02-03 13:04:54 +0000 |
| commit | 207f943e2c7ffa4f8eced38c846c6b31e3cdbc77 (patch) | |
| tree | aa4c21713b2ffd5760e110d25af1aae8c0d5f97f /include | |
| parent | fmt: preprocessor statements (diff) | |
| download | soyuz-207f943e2c7ffa4f8eced38c846c6b31e3cdbc77.tar.xz soyuz-207f943e2c7ffa4f8eced38c846c6b31e3cdbc77.zip | |
fix(#1): delete_handle generating junk data when lunar is closed after first pid check
Soyuz does an initial PID check after launching to make sure that Lunar Client is open, which takes care of most errors, at least I thought. However, within my limited testing I guess it never crossed my mind to check what would happen if I closed Lunar Client **after** Soyuz had been initialized...
Turns out it just generates seemingly infinite errors logs as it has no valid PID to operate on.
This commit patches the aforementioned bug by introducing another PID check before every iteration that the delete_handle function should run, as well as a timeout.
Thanks to @LorenzoHanssens for filling a bug report! (#1)
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions