[
https://issues.apache.org/jira/browse/GUACAMOLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175273#comment-16175273
]
Michael Jumper commented on GUACAMOLE-384:
------------------------------------------
Unfortunately, that all looks fine ... no bad values, no crazy width that
could lead to an overflow. If the memory allocated for the buffer became
invalid due to a free() in another thread, this might make sense.
Otherwise, except that you report it has segfaulted at this point, this
looks absolutely normal.
Have you tried reproducing this under valgrind? That might reveal what's
going on.
> 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: guacd
> 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)
