[jira] [Resolved] (GUACAMOLE-1259) Son of immediate double-free upon connecting to Windows RDP

["Mike Jumper (Jira)" <ji...@apache.org>]

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

Mike Jumper resolved GUACAMOLE-1259.
------------------------------------
    Fix Version/s: 1.4.0
       Resolution: Fixed

> Son of immediate double-free upon connecting to Windows RDP
> -----------------------------------------------------------
>
>                 Key: GUACAMOLE-1259
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1259
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: RDP
>    Affects Versions: 1.3.0
>            Reporter: Mike Jumper
>            Assignee: Mike Jumper
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> From GUACAMOLE-1241:
> {quote}
> Regression testing against {{staging/1.3.0}} using the Docker image, I am seeing an immediate disconnect due to a double-free when attempting to connect to Windows RDP:
> {code:none}
> ...
> guacd[24698]: INFO:	Loading keymap "base"
> guacd[24698]: INFO:	Loading keymap "en-us-qwerty"
> guacd[24698]: INFO:	Connected to RDPDR 1.13 as client 0x0005
> free(): double free detected in tcache 2
> guacd[6]: INFO:	Connection "$e6955582-c6f2-4912-a4bd-a3ffee002cd1" removed.
> {code}
> With there being a few memory-related RDP changes in the upcoming release (and with no such issues in 1.2.0), I suspect this is a regression.
> {quote}
> This is still happening when building against FreeRDP 2.0.0-rc4, not because things are incorrectly detected at build time, but because the {{config.h}} header containing the macro resulting from that detection is not included in the relevant file. The call to {{Stream_Free()}} therefore always occurs, even if FreeRDP was detected as doing this automatically.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)