[
https://issues.apache.org/jira/browse/GUACAMOLE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297056#comment-15297056
]
Michael Jumper commented on GUACAMOLE-33:
-----------------------------------------
This is caused by the lack of a mechanism to signal {{guac_common_cursor}} of a
leaving user. Such a mechanism used to exist, but was removed when thought
unnecessary.
It turns out this is actually necessary, as there is otherwise no guarantee
that a newly-allocated user will have a different memory address from the user
that just left, and thus certain cursor updates (such as the setting of
opacity) may be omitted under the assumption that the user must be the same.
*This assumption can fail frequently*, as the memory manager will often service
a memory allocation request using a recently-freed memory block.
> Duplicate mouse cursors
> -----------------------
>
> Key: GUACAMOLE-33
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-33
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server
> Reporter: Michael Jumper
> Priority: Critical
>
> After joining a connection (any protocol), if the browser tab is reloaded, a
> duplicate (software) mouse cursor is shown after the connection is
> reestablished. It does not vanish when the mouse leaves the browser window.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
