[
https://issues.apache.org/jira/browse/GUACAMOLE-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878943#comment-17878943
]
Lukas Raska commented on GUACAMOLE-1256:
----------------------------------------
[~mjumper]
[https://github.com/apache/guacamole-server/commit/8ba29b25e78235c0fd72361d75ef3e2e4bd83f22]
(as part of the linked PR
[https://github.com/apache/guacamole-server/pull/528] ). It adds flush display
calls for every _guac_terminal_scroll_down_ and _guac_terminal_scroll_up._
While for the _guac_terminal_scroll_down_ it doesn't have that much of an
impact and solves the scrolling issue in vi (at least what I've tested), for
the _guac_terminal_scroll_up_ it causes the performance degradation since I
presume it gets called every time the content switches by one line down (which
in case of dumping text file / looking up logs via journalctl or docker logs /
or even running dmesg is very unfortunate)
> Lines of file gets broken when navigating back and forth using a text editor
> ----------------------------------------------------------------------------
>
> Key: GUACAMOLE-1256
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1256
> Project: Guacamole
> Issue Type: Bug
> Components: Terminal
> Affects Versions: 1.2.0
> Environment: Distributor ID:Ubuntu
> Description:Ubuntu 18.04.2 LTS
> Release:18.04
> Codename:bionic
> Linux dev-kubernetes-01 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Hugaleno Bezerra
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: Screenshot from 2023-10-10 13-39-18.png, Screenshot from
> 2023-10-10 13-41-00.png, bug_scrollingback_onfile.gif,
> image-2024-06-06-18-13-06-244.png
>
>
> Protocol: SSH
> When editing a file using a text editor like vim and navigating back and
> forth in the file some lines get "broken".
> The file being used in the gif below is a default file from ubuntu
> installation "vim /etc/ltrace.conf"
> The problem happens in some servers of our local network, while in anothers
> with same SO it doens't. We tried find a step to step to reproduce the
> problem with 100% accurate but unfortunately we couldn't.
> We decide to share that to see if someone else is having the same problem and
> could help to find the reason.
> If you need any more information to help reproduce de problem pls let me know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
