Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 13
Affects Version/s: 13
Component/s: hotspot
Labels:
- gc-pending-review

Subcomponent:
gc
Resolved In Build:
b28

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8227193	14	Kim Barrett	P3	Resolved	Fixed	b05
JDK-8228282	13.0.2	Kim Barrett	P3	Resolved	Fixed	b01
JDK-8228066	13.0.1	Kim Barrett	P3	Resolved	Fixed	master

Instrumenting the ServiceThread's OopStorage cleanup handling, we see the thread spins or gets woken up a lot during ordinary operation (not stress tests or the like). There shouldn't be that much to do, so we're likely wasting CPU cycles.

backported by

JDK-8227193 Excessive ServiceThread wakeups for OopStorage cleanup

Resolved

JDK-8228066 Excessive ServiceThread wakeups for OopStorage cleanup

Resolved

JDK-8228282 Excessive ServiceThread wakeups for OopStorage cleanup

Resolved

blocks

JDK-8226794 OopStorage concurrent iteration always requests cleanup

Open

JDK-8226796 Reduce debug level logging for oopstorage+blocks

Resolved

relates to

JDK-8224847 gc/stress/TestReclaimStringsLeaksMemory.java fails with reserved greater than expected

Resolved

JDK-8227053 ServiceThread cleanup of OopStorage is missing some

Resolved

JDK-8227054 ServiceThread needs to know about all OopStorage objects

Resolved

JDK-8231612 100% cpu on arm32 in Service Thread

Closed

(4 relates to)

Assignee:: Kim Barrett

Reporter:: Kim Barrett

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2019-06-18 19:00

Updated:: 2019-09-30 23:21

Resolved:: 2019-07-02 15:31

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates