[
https://issues.apache.org/jira/browse/GUACAMOLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189117#comment-16189117
]
Michael Jumper commented on GUACAMOLE-384:
------------------------------------------
Looks like the terminal is being freed during normal connection cleanup, but
prior to the SSH client thread finishing. Depending on timing, attempts to
write to the terminal by the SSH client thread segfault since the terminal was
already freed.
This needs to be fixed, but will not affect the stability of connections in
practice, as the segfault is occurring during normal disconnect.
> Guacd crashes in buffer.c during stress test
> ---------------------------------------------
>
> 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: Blocker
>
> 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)
