Bug 65111 - Possible memory leak in AprEndpoint - socketBufferHandler is not cleared
Summary: Possible memory leak in AprEndpoint - socketBufferHandler is not cleared
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 9
Classification: Unclassified
Component: Util (show other bugs)
Version: 9.0.x
Hardware: PC All
: P2 normal (vote)
Target Milestone: -----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-28 12:43 UTC by Roman
Modified: 2021-01-28 15:00 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman 2021-01-28 12:43:27 UTC 
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.
Comment 1 Remy Maucherat 2021-01-28 15:00:46 UTC 
I think this looks like a problem. The fix will be 10.0.2, 9.0.43 and 8.5.63.