On 24/01/2019 13:01, Rainer Jung wrote: > Am 24.01.2019 um 13:37 schrieb Mark Thomas:
<snip/> >> It can happen in normal usage. I saw it once. It happens on Connector >> stop so it could be worse. My memory leak fix is definitely the root >> cause. Any thoughts on a possible fix? > > Currently experimenting with a cleanup handler registered for con->pool. > That can get an arbitrary argument and is called when the cleanup > happens, especially useful for the problematic cleanup as a child pool. > The handler could overwrite con->pool with NULL. But that would only > make sense, if we are sure, that we are notgoing to use stuff after > OpenSSLContext.destroy(). That handler sounds like the way to go. Remove the reference to the pool when it is cleaned up. I'm reasonable sure that there isn't any usage of the pool after that point else we'd be seeing crashes all over the place. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
