While the issue may correlate with the release of 1.5.4, keep in mind
that the log message in question is coming from FreeRDP regarding memory
that FreeRDP itself manages, and it is reporting what FreeRDP identifies
as a possible bug *in itself*. See:
https://lists.apache.org/thread/9xws51d32h6mqz35d9odh2kwnl04g8p9
If you suspect this is not the case, then you would need to eliminate
FreeRDP as a possible cause by rebuilding the 1.5.4 guacd image against
the same version of FreeRDP used by 1.5.3 (using the "WITH_FREERDP"
build arg). The version of FreeRDP available at the time 1.5.3 was
released was "2.10.0".
Pointing to the 1.5.3 image does not just roll back to a previous
version of Guacamole; it rolls back to the previous version of
*everything available at the time*, including FreeRDP.
- Mike
On 1/2/24 06:28, Anders Fogh Eriksen wrote:
We just tried rolling back to 1.5.3 and that fixes our issue.
It seems like 1.5.4 contains a lot of changes related to memory
management:
https://github.com/apache/guacamole-server/compare/1.5.3...1.5.4#
<https://github.com/apache/guacamole-server/compare/1.5.3...1.5.4#>
On 2024/01/02 13:46:06 Vieri wrote:
>
> From the OP it seems that guacamole 1.5.3 did not have this issue,
but it is yet to be confirmed.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
