[jira] [Updated] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Bean updated GUACAMOLE-709: - Attachment: Screen Shot 2019-01-20 at 1.41.34 PM.png > 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)
[jira] [Updated] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Bean updated GUACAMOLE-709: - Attachment: Screen Shot 2019-01-20 at 1.43.16 PM.png > 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)
[jira] [Updated] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Bean updated GUACAMOLE-709: - Attachment: Screen Shot 2019-01-20 at 1.41.34 PM.png > 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.41.34 PM.png, Screen Shot 2019-01-20 at 1.43.16 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)
[jira] [Updated] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Bean updated GUACAMOLE-709: - Attachment: Screen Shot 2019-01-20 at 1.43.16 PM.png > 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.41.34 PM.png, Screen Shot 2019-01-20 at 1.43.16 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)
[jira] [Commented] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747533#comment-16747533 ] Jason Bean commented on GUACAMOLE-709: -- Ok, here is a snapshot after running for a while. Should this sawtooth pattern be normal? I realize it's doing garbage collection at the tip of the sawtooth but why is it growing? I'm using the MySQL and DUO plugins. What else do I need to look at within VisualVM? I've also attached a screenshot of top within the container. The java process is currently using 1.1GB. This is just sitting idle. !Screen Shot 2019-01-20 at 1.41.34 PM.png!!Screen Shot 2019-01-20 at 1.43.16 PM.png! > 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.41.34 PM.png, Screen Shot 2019-01-20 at 1.43.16 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)
[jira] [Comment Edited] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747533#comment-16747533 ] Michael Jumper edited comment on GUACAMOLE-709 at 1/20/19 8:08 PM: --- Ok, here is a snapshot after running for a while. Should this sawtooth pattern be normal? I realize it's doing garbage collection at the tip of the sawtooth but why is it growing? I'm using the MySQL and DUO plugins. What else do I need to look at within VisualVM? I've also attached a screenshot of top within the container. The java process is currently using 1.1GB. This is just sitting idle. !Screen Shot 2019-01-20 at 1.41.34 PM.png|width=100%! !Screen Shot 2019-01-20 at 1.43.16 PM.png! was (Author: taddeusz): Ok, here is a snapshot after running for a while. Should this sawtooth pattern be normal? I realize it's doing garbage collection at the tip of the sawtooth but why is it growing? I'm using the MySQL and DUO plugins. What else do I need to look at within VisualVM? I've also attached a screenshot of top within the container. The java process is currently using 1.1GB. This is just sitting idle. !Screen Shot 2019-01-20 at 1.41.34 PM.png!!Screen Shot 2019-01-20 at 1.43.16 PM.png! > 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.41.34 PM.png, Screen Shot 2019-01-20 at 1.43.16 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)
[jira] [Updated] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Bean updated GUACAMOLE-709: - Attachment: (was: Screen Shot 2019-01-20 at 1.43.16 PM.png) > 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)
[jira] [Updated] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Bean updated GUACAMOLE-709: - Attachment: (was: Screen Shot 2019-01-20 at 1.41.34 PM.png) > 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)
[jira] [Commented] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747541#comment-16747541 ] Michael Jumper commented on GUACAMOLE-709: -- {quote} Should this sawtooth pattern be normal? {quote} The sawtooth pattern of heap consumption is normal for any Java application, yes. Under normal, healthy operation, you will see heap consumption grow until it reaches a threshold where the JVM performs a GC. Here's a decent post going over the characteristics of leaky and non-leaky graphs: https://plumbr.io/blog/memory-leaks/memory-leaks-fallacies-and-misconceptions {quote} I realize it's doing garbage collection at the tip of the sawtooth but why is it growing? {quote} Java will not free up heap immediately. It waits for what the JVM deems is an opportune time to perform a GC and free up heap. What you are observing is not the heap _growing_ but the heap being _used_, which just about every Java function call will do. If heap usage were growing, the valley of the sawtooth would be gradually higher each time. You may see some different behavior with newer JVMs with respect to the nature and timing of that GC, but what you're seeing here is normal and not indicative of a leak. If you still suspect a leak, what you need to do is run things with VisualVM through multiple GC cycles (probably several hours at the rate shown in your graph), and see whether the graph still looks healthy. > 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)
[jira] [Commented] (GUACAMOLE-709) Possible Client Memory Leak
[ https://issues.apache.org/jira/browse/GUACAMOLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747547#comment-16747547 ] Jason Bean commented on GUACAMOLE-709: -- I'll continue to keep an eye on it. I have VisualVM running inside one of my VM's so I can keep in running. > 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)
[jira] [Created] (GUACAMOLE-710) Connection to TigerVNC drops shortly after connection
Kenzie Togami created GUACAMOLE-710: --- Summary: Connection to TigerVNC drops shortly after connection Key: GUACAMOLE-710 URL: https://issues.apache.org/jira/browse/GUACAMOLE-710 Project: Guacamole Issue Type: Bug Components: VNC Affects Versions: 1.0.0 Environment: Docker images: mysql:8, guacd:1.0.0 ,guacamole:1.0.0. socat from alpine:3.8. Host machine: Ubuntu 18.10 "Cosmic Cuttlefish". Docker 18.09.1. Reporter: Kenzie Togami Guacamole is disconnecting me from my VNC server after a few seconds of connection. I get fine streaming, but then the connection suddenly disappears. Logs don't show much: [https://gist.github.com/kenzierocks/0e1f86d3850497f5f7438709b0811641|https://gist.github.com/kenzierocks/0e1f86d3850497f5f7438709b0811641.]. I am streaming this in a bit of weird setup, but I don't think it should cause any issues. Basically I host TigerVNC on my machine, then Guacamole runs in a Docker container, and to avoid exposing the port I pipe the VNC data through socat in another docker container. This means the flow of data is VNC -> Docker networking -> socat -> Docker networking -> guacd, but I don't think this should result in random disconnects. socat reports that the sockets are reaching EOF. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-710) Connection to TigerVNC drops shortly after connection
[ https://issues.apache.org/jira/browse/GUACAMOLE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747729#comment-16747729 ] Michael Jumper commented on GUACAMOLE-710: -- {quote} I am streaming this in a bit of weird setup, but I don't think it should cause any issues. {quote} What have you done so far to eliminate that as the cause? Given the [fundamental nature of the feature in question|http://guacamole.apache.org/faq/#probably-not-a-bug] and the uniqueness of what you're doing here, some unexpected behavior of that "Docker -> socat -> Docker" portion seems more likely. {quote} ... to avoid exposing the port ... {quote} If Guacamole is running beneath Docker on the same machine as TigerVNC, I'm not sure what you're trying to avoid exposing. Any Docker container on that machine will be able to connect to your TigerVNC using the IP address of the Docker interface. > Connection to TigerVNC drops shortly after connection > - > > Key: GUACAMOLE-710 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-710 > Project: Guacamole > Issue Type: Bug > Components: VNC >Affects Versions: 1.0.0 > Environment: Docker images: mysql:8, guacd:1.0.0 ,guacamole:1.0.0. > socat from alpine:3.8. > Host machine: Ubuntu 18.10 "Cosmic Cuttlefish". Docker 18.09.1. >Reporter: Kenzie Togami >Priority: Major > > Guacamole is disconnecting me from my VNC server after a few seconds of > connection. I get fine streaming, but then the connection suddenly > disappears. Logs don't show much: > [https://gist.github.com/kenzierocks/0e1f86d3850497f5f7438709b0811641|https://gist.github.com/kenzierocks/0e1f86d3850497f5f7438709b0811641.]. > I am streaming this in a bit of weird setup, but I don't think it should > cause any issues. Basically I host TigerVNC on my machine, then Guacamole > runs in a Docker container, and to avoid exposing the port I pipe the VNC > data through socat in another docker container. This means the flow of data > is VNC -> Docker networking -> socat -> Docker networking -> guacd, but I > don't think this should result in random disconnects. socat reports that the > sockets are reaching EOF. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-710) Connection to TigerVNC drops shortly after connection
[ https://issues.apache.org/jira/browse/GUACAMOLE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-710: - Description: Guacamole is disconnecting me from my VNC server after a few seconds of connection. I get fine streaming, but then the connection suddenly disappears. Logs don't show much: [^guacd.log]. I am streaming this in a bit of weird setup, but I don't think it should cause any issues. Basically I host TigerVNC on my machine, then Guacamole runs in a Docker container, and to avoid exposing the port I pipe the VNC data through socat in another docker container. This means the flow of data is VNC -> Docker networking -> socat -> Docker networking -> guacd, but I don't think this should result in random disconnects. socat reports that the sockets are reaching EOF. (was: Guacamole is disconnecting me from my VNC server after a few seconds of connection. I get fine streaming, but then the connection suddenly disappears. Logs don't show much: [https://gist.github.com/kenzierocks/0e1f86d3850497f5f7438709b0811641|https://gist.github.com/kenzierocks/0e1f86d3850497f5f7438709b0811641.]. I am streaming this in a bit of weird setup, but I don't think it should cause any issues. Basically I host TigerVNC on my machine, then Guacamole runs in a Docker container, and to avoid exposing the port I pipe the VNC data through socat in another docker container. This means the flow of data is VNC -> Docker networking -> socat -> Docker networking -> guacd, but I don't think this should result in random disconnects. socat reports that the sockets are reaching EOF.) > Connection to TigerVNC drops shortly after connection > - > > Key: GUACAMOLE-710 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-710 > Project: Guacamole > Issue Type: Bug > Components: VNC >Affects Versions: 1.0.0 > Environment: Docker images: mysql:8, guacd:1.0.0 ,guacamole:1.0.0. > socat from alpine:3.8. > Host machine: Ubuntu 18.10 "Cosmic Cuttlefish". Docker 18.09.1. >Reporter: Kenzie Togami >Priority: Major > Attachments: guacd.log > > > Guacamole is disconnecting me from my VNC server after a few seconds of > connection. I get fine streaming, but then the connection suddenly > disappears. Logs don't show much: [^guacd.log]. I am streaming this in a bit > of weird setup, but I don't think it should cause any issues. Basically I > host TigerVNC on my machine, then Guacamole runs in a Docker container, and > to avoid exposing the port I pipe the VNC data through socat in another > docker container. This means the flow of data is VNC -> Docker networking -> > socat -> Docker networking -> guacd, but I don't think this should result in > random disconnects. socat reports that the sockets are reaching EOF. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-710) Connection to TigerVNC drops shortly after connection
[ https://issues.apache.org/jira/browse/GUACAMOLE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-710: - Attachment: guacd.log > Connection to TigerVNC drops shortly after connection > - > > Key: GUACAMOLE-710 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-710 > Project: Guacamole > Issue Type: Bug > Components: VNC >Affects Versions: 1.0.0 > Environment: Docker images: mysql:8, guacd:1.0.0 ,guacamole:1.0.0. > socat from alpine:3.8. > Host machine: Ubuntu 18.10 "Cosmic Cuttlefish". Docker 18.09.1. >Reporter: Kenzie Togami >Priority: Major > Attachments: guacd.log > > > Guacamole is disconnecting me from my VNC server after a few seconds of > connection. I get fine streaming, but then the connection suddenly > disappears. Logs don't show much: > [https://gist.github.com/kenzierocks/0e1f86d3850497f5f7438709b0811641|https://gist.github.com/kenzierocks/0e1f86d3850497f5f7438709b0811641.]. > I am streaming this in a bit of weird setup, but I don't think it should > cause any issues. Basically I host TigerVNC on my machine, then Guacamole > runs in a Docker container, and to avoid exposing the port I pipe the VNC > data through socat in another docker container. This means the flow of data > is VNC -> Docker networking -> socat -> Docker networking -> guacd, but I > don't think this should result in random disconnects. socat reports that the > sockets are reaching EOF. -- This message was sent by Atlassian JIRA (v7.6.3#76005)