You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Nick Couchman (JIRA)" <ji...@apache.org> on 2019/01/22 14:50:00 UTC
[jira] [Reopened] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Couchman reopened GUACAMOLE-709:
-------------------------------------
> Possible Client Memory Leak
> ---------------------------
>
> Key: GUACAMOLE-709
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-709
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-client
> Affects Versions: 1.0.0
> Environment: Docker, debian:stable base
> Reporter: Jason Bean
> Priority: Major
> Attachments: Screen Shot 2019-01-20 at 1.41.34 PM.png, Screen Shot 2019-01-20 at 1.43.16 PM.png
>
>
> I have an all-in-one Docker I created, jasonbean/guacamole, and since I modified it for 1.0.0 I'm seeing tomcat's java process using as much as 2.5GB of memory. It starts at around 800MB.
> Since it's an all-in-one container I'm using debian:stable as the base and using tomcat8 and java from the Debian repository. Do I need to be doing something differently or could this be a problem with the client code?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)