You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the target process is unable to handle the message, which always happens eventually either when the target isn't controlled by you, or the system is under load, or the target has crashed - the sending node app will then wait infinitely for SendMessageW to return, and it never does.
I went through win32-api's src and SendMessageTimeoutW is missing, if time permits I would very much appreciate if someone added it, because it would solve exactly these issues in a very critical part of my stack.
Also willing to pay a bounty for whoever adds it!
Thank you
The text was updated successfully, but these errors were encountered:
If the target process is unable to handle the message, which always happens eventually either when the target isn't controlled by you, or the system is under load, or the target has crashed - the sending node app will then wait infinitely for SendMessageW to return, and it never does.
I went through win32-api's src and SendMessageTimeoutW is missing, if time permits I would very much appreciate if someone added it, because it would solve exactly these issues in a very critical part of my stack.
Also willing to pay a bounty for whoever adds it!
Thank you
The text was updated successfully, but these errors were encountered: