You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2017/10/03 00:35:01 UTC

[jira] [Updated] (GUACAMOLE-384) Terminal writes during disconnect may segfault

     [ https://issues.apache.org/jira/browse/GUACAMOLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Jumper updated GUACAMOLE-384:
-------------------------------------
    Summary: Terminal writes during disconnect may segfault  (was: Guacd crashes in buffer.c during stress test )

> Terminal writes during disconnect may segfault
> ----------------------------------------------
>
>                 Key: GUACAMOLE-384
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-384
>             Project: Guacamole
>          Issue Type: Bug
>          Components: Terminal
>    Affects Versions: 0.9.12-incubating
>         Environment: GNU/Linux x86_64
>            Reporter: Phillip Arcuri
>            Priority: Minor
>
> In a stress test we kick off an SSH session every second.  The session does a minimal amount of work and exits after a few seconds.  A ps -ef shows we have 2 to 6 instances running at one time.  About 1 in 10 of the instances cores with corrupted buffer data at line buffer.c:108.:
> (gdb) p *buffer
> $2 = {default_character = {value = -1269703408, attributes = {bold = 170, reverse = 42, cursor = false, underscore = false, foreground = 0,
>       background = 0}, width = -1269422328}, rows = 0x2aaab456fa30, top = 686, length = 0, available = 686}
> As an aside I also see roughly 1 in 100 instances become a zombie process hung in pthread_join.  Doubt that is related, but thought I'd mention it.
> This is a blocker for our deployment of a guacamole-enabled feature-set.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)