| Summary: | Possible memory leak in AprEndpoint - socketBufferHandler is not cleared | ||
|---|---|---|---|
| Product: | Tomcat 9 | Reporter: | Roman <roman.vidert> |
| Component: | Util | Assignee: | Tomcat Developers Mailing List <dev> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 9.0.x | ||
| Target Milestone: | ----- | ||
| Hardware: | PC | ||
| OS: | All | ||
I think this looks like a problem. The fix will be 10.0.2, 9.0.43 and 8.5.63. Thanks, this solved the issue for me. |
In my application, the capacity of used memory by direct buffer pools is increasing over time, after some research I found that in AprEndpoint in method doClose "socketBufferHandler" is not executing "free()" method call, and the link is just set to "EMPTY": > socketBufferHandler = SocketBufferHandler.EMPTY; Because of this allocated native memory is not released.