[Bug 57546] Memory Leak in SecureNioChannel

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546 Mark Thomas changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 57546] Memory Leak in SecureNioChannel

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546 chinanzio changed: What|Removed |Added Priority|P2 |P1

[Bug 57546] Memory Leak in SecureNioChannel

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #15 from Jan --- Hi, I'm afraid we're facing the same problem with Tomcat 7.0.67 and 8.0.32. Paul, can you confirm that this bug is fixed now? -- You are receiving this mail because: You are the

[Bug 57546] Memory Leak in SecureNioChannel

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #14 from Mark Thomas ma...@apache.org --- (In reply to Paul Gaylie from comment #13) Created attachment 32854 [details] Screen Shot from hprof Guys, Please consider using a more gender neutral form of address when addressing

[Bug 57546] Memory Leak in SecureNioChannel

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546 Paul Gaylie paul.gay...@gmail.com changed: What|Removed |Added CC|

[Bug 57546] Memory Leak in SecureNioChannel

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #11 from Paul Gaylie paul.gay...@gmail.com --- Mark, It looks like you fixed this is version 8.0.19 but this version is not released. Any time frame when this fix will be available? Thanks, Paul -- You are receiving this mail

[Bug 57546] Memory Leak in SecureNioChannel

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #12 from Chuck Caldarale chuck.caldar...@unisys.com --- (In reply to Paul Gaylie from comment #11) It looks like you fixed this is version 8.0.19 but this version is not released. Any time frame when this fix will be available?

[Bug 57546] Memory Leak in SecureNioChannel

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546 Mark Thomas ma...@apache.org changed: What|Removed |Added CC|

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #9 from Mark Thomas ma...@apache.org --- See r1658734 and r1658790. -- You are receiving this mail because: You are the assignee for the bug. - To

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #8 from Paul Gaylie paul.gay...@gmail.com --- Hi Mark, Great that you found the bug. Exactly what code needed to be updated? Just curious where the proper fix needed to be applied - was driving me nuts. -- You are receiving

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #3 from Mark Thomas ma...@apache.org --- (In reply to Paul Gaylie from comment #2) Mark, Unfortunately, killing a browser is not a good simulation because the browser is smart enough to properly close the websocket when it

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #4 from Mark Thomas ma...@apache.org --- Interesting. I tried testing with a separate machine so I could pull out the network cable. That has triggered a problem that looks like the one described here. I'm looking into this at

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 Konstantin Kolinko knst.koli...@gmail.com changed: What|Removed |Added Status|RESOLVED

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #1 from Mark Thomas ma...@apache.org --- release() isn't expected to be called for an HTTP upgrade connection so that method getting called is not part of the problem. I've tried to reproduce this with 8.0.x trunk but I can't.

[Bug 57546] Memory Leak in SecureNioChannel

https://issues.apache.org/bugzilla/show_bug.cgi?id=57546 --- Comment #2 from Paul paul.gay...@gmail.com --- Mark, Unfortunately, killing a browser is not a good simulation because the browser is smart enough to properly close the websocket when it gets killed. Here is what to do: connect using