Reduce delay before app closes on windows

[Spishous]

Description

in certain Windows configurations, the signal expected by "WaitForSingleObject" before closing the application window (when "exitProcessOnClose" is true in neutralino.config.json), is not received. Which creates a freeze lasting from 2sec to 10sec on some machines. #1179

Changes proposed

• Reduced WaitForSingleObject delay

Next steps

I don't know enough about C++ to delve deeper into the problem. But the next step would be to see why when "exitProcessOnClose" is true, the behavior of the closure changes and blocks at this step.

None.

[Spishous]

@nicorac

[nicorac]

Well, the WaitForSingleObject delay is not really a "delay" but a timeout: the function waits for at most 10000ms for the watched handle to be released (at window destruction).
It was added because the applicaiton did not correctly release its resources, leading to handle leaks.

That said, the question is: is this new behavior related to Windows 11?
The OP of #1179 runs Win11, but others not, so I'm not sure...

Sadly I'm actually not able to further investigate on it, I'm sorry 😔

[moritz-baecker-integra]

Well, the WaitForSingleObject delay is not really a "delay" but a timeout: the function waits for at most 10000ms for the watched handle to be released (at window destruction). It was added because the applicaiton did not correctly release its resources, leading to handle leaks.

That said, the question is: is this new behavior related to Windows 11? The OP of #1179 runs Win11, but others not, so I'm not sure...

Sadly I'm actually not able to further investigate on it, I'm sorry 😔

This behavior also happens on Windows 10 (Version 10.0.19045 Build 19045). I have to wait multiple seconds for the window to close.

[AntumDeluge]

Same here, on Windows 10.

[shalithasuranga]

Thanks so much @Spishous for sending this pull request 🎉