Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P2
Fix Version/s: 20
Affects Version/s: 20
Component/s: hotspot
Labels:

Subcomponent:
runtime
Resolved In Build:
b28

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8298666	21	Coleen Phillimore	P2	Resolved	Fixed	b02

LSan has hinted at a memory leak in MethodData related to _extra_data_lock. It looks like MethodData::deallocate_contents is being called before ~MethodData from Method::release_C_heap_structures(), leading to the memory used by _extra_data_lock not being released.

I confirmed this by switching _extra_data_lock to be a pointer and adding a guarantee to MethodData::deallocate_contents that asserts it should be NULL. It crashes at the guarantee. I'll see if I can get the call trace.

backported by

JDK-8298666 Memory leak in Method::build_profiling_method_data

Resolved

relates to

JDK-8297389 resexhausted003 fails with assert(!thread->owns_locks()) failed: must release all locks when leaving VM

Resolved

JDK-8298346 Metaspace object lifetime management is convoluted

Closed

links to

Commit openjdk/jdk20/04b8d0cf

Review openjdk/jdk20/13

Review openjdk/jdk/11526

(1 links to)

Assignee:: Coleen Phillimore

Reporter:: Justin King

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2022-12-04 22:41

Updated:: 2022-12-20 11:36

Resolved:: 2022-12-13 05:04

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates