[
https://issues.apache.org/jira/browse/GUACAMOLE-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Jumper closed GUACAMOLE-1846.
----------------------------------
Resolution: Fixed
The failure above is not due to these changes, but due to a line from
GUACAMOLE-377 that is no longer needed following merge of these changes. We
should address that through changes under GUACAMOLE-377. Nothing further needed
here.
> Race condition can cause the first user for a connection to miss updates
> ------------------------------------------------------------------------
>
> Key: GUACAMOLE-1846
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1846
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server
> Reporter: James Muehlner
> Priority: Minor
> Fix For: 1.5.4
>
>
> The changes in https://github.com/apache/guacamole-server/pull/39 seem to
> have introduced a potential race condition where the client thread may write
> updates to the broadcast socket before the first user (the owner) is added to
> the user list.
> This change was made nearly 7 years ago, and I never noticed it before
> testing my changes in https://github.com/apache/guacamole-server/pull/454, so
> it's fair to say that it doesn't happen very often. I only see it maybe 10%
> of the time, and only with an RDP connection using the Cygwin build of
> guacamole-server.
> The symptoms are that nothing but a blank screen is rendered.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
