[
https://issues.apache.org/jira/browse/GUACAMOLE-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Ionita updated GUACAMOLE-1774:
---------------------------------------
Description:
{{InputSink}} attaches a {{keydown}} event listener to document to re-focus the
sink field. However it doesn't check if the field is attached to the DOM, which
means that if you re-create the sink and the Guacamole client, the old sink
will still get keydown events and will still attempt to re-focus the old sink
input field, despite it no longer being in the DOM.
Detected in 1.4, existing in later versions too.
was:
{{InputSink}} attaches a {{keydown}} event listener to document to re-focus the
sink field. However it doesn't check if the field is attached to the DOM, which
means that if you re-create the sink and the Guacamole client, the old sink
will still key keydown events and will still attempt to re-focus the old sink
input field, despite it no longer being in the DOM.
Detected in 1.4, existing in later versions too.
> guacamole-client InputSink memory leak
> --------------------------------------
>
> Key: GUACAMOLE-1774
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1774
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client
> Affects Versions: 1.4.0, 1.5.0, 1.5.1
> Reporter: Valentin Ionita
> Priority: Minor
> Labels: performance
>
> {{InputSink}} attaches a {{keydown}} event listener to document to re-focus
> the sink field. However it doesn't check if the field is attached to the DOM,
> which means that if you re-create the sink and the Guacamole client, the old
> sink will still get keydown events and will still attempt to re-focus the old
> sink input field, despite it no longer being in the DOM.
>
> Detected in 1.4, existing in later versions too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)