spring boot version: 2.3.6.RELEASE

The application's memory footprint was always high, so I downloaded the memory dump file and used mat's analysis results to point to the classloader 。

图片 图片 图片 图片 图片

Comment From: wilkinsona

Thanks for the report but I can't see anything unusual here. LaunchedURLClassLoader has loaded the classes for 30,037 objects and those objects are consuming 79,957,808MB of heap. I don't think that indicates that there's a problem with the class loader. There may be a problem with the classes that it's loaded but it could equally be normal behaviour: it's impossible to tell from the information you've provided thus far.

Please note that Spring Boot 2.3.6 has reached the end of its OSS support period. Please upgrade to Spring Boot 2.5.x or 2.6.x. If the problem that you are seeing remains once you have upgraded, please explain why you believe there's a problem with LaunchedURLClassLoader.

Comment From: spring-projects-issues

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Comment From: spring-projects-issues

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.

Comment From: 411937647

Thank you for your reply. I will reorient my question.

Comment From: mmylili

Thank you for your reply. I will reorient my question. so, at the last, whats the problem?