-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow a zero timeout for g_obj_wait() #2904
Allow a zero timeout for g_obj_wait() #2904
Conversation
- Mostly base functions and utilities necessary to enable RFX Progressive - Add more EGFX work & mode flags. - Update encoder. - Does not yet include caps determination to enable RFX progressive (yet). - Update protocol constants
- Introduce functional EGFX caps. - Prototype of RFX Progressive working. - Update resizing to work with it. - Refactoring
While doing this I've discovered the timer queue processing in chansrv can be significantly improved. I'll fix that in devel at some stage |
Yes, FreeBSD 12 is EoL'd |
@matt335672 Could you cherry-pick 05c78bb to |
At the moment, timeouts of -1 or 0 for g_obj_wait() both mean 'no timeout', i.e. wait forever. This commit changes a timeout of 0 to mean 'return immediately'. This is more consistent with poll() and WaitForMultipleObjects(), and can be used by the new encoder logic. There are a very few places on xrdp where a timeout of 0 is currently specified to mean 'wait forever'. These are replaced with values of -1.
db3aaec
to
170b881
Compare
5814809
to
aafb6d3
Compare
Will update |
This PR looks good to me, but for some reason I don't understand why the diff has changes in it that it shouldn't. This should just apply to the g_obj_wait changes? Right? |
This is what you intended to change, correct? 353d76f |
I'll delete this now - @Nexarian has already merged it. |
At the moment, timeouts of -1 or 0 for g_obj_wait() both mean 'no timeout', i.e. wait forever. This commit changes a timeout of 0 to mean 'return immediately'. This is more consistent with poll() and WaitForMultipleObjects(), and can be used by the new encoder logic.
There are a very few places on xrdp where a timeout of 0 is currently specified to mean 'wait forever'. These are replaced with values of -1.