Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 20
Affects Version/s: 11, 17, 19, 20
Component/s: hotspot
Labels:

Subcomponent:
jfr
Resolved In Build:
b17
CPU:

ppc

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8294756	17.0.6	Martin Doerr	P3	Resolved	Fixed	b01
JDK-8295002	11.0.18	Martin Doerr	P3	Resolved	Fixed	b01

The assertion was hit in JavaThread::pd_get_top_frame_for_profiling (after ~~JDK-8290004~~ was fixed) while testing jdk/jfr/api/consumer/log/TestSystemEvents.java.

The acquire barrier from ~~JDK-8290004~~ has helped, but not fixed all problems. "last_Java_pc" can still be observed as 0 in rare cases because not all writers use a release barrier.

backported by

JDK-8294756 [PPC64] JfrGetCallTrace: assert(_pc != nullptr) failed: must have PC

Resolved

JDK-8295002 [PPC64] JfrGetCallTrace: assert(_pc != nullptr) failed: must have PC

Resolved

clones

JDK-8290004 [PPC64] JfrGetCallTrace: assert(_pc != nullptr) failed: must have PC

Resolved

relates to

JDK-8295872 [PPC64] JfrGetCallTrace: Need pc == nullptr check before frame constructor

Resolved

links to

Commit openjdk/jdk11u-dev/9014a180

Commit openjdk/jdk17u-dev/90cc8ac9

Commit openjdk/jdk/14c6ac45

Review openjdk/jdk11u-dev/1390

Review openjdk/jdk17u-dev/740

Review openjdk/jdk/10339

(5 links to)

Assignee:: Martin Doerr

Reporter:: Martin Doerr

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2022-09-19 03:56

Updated:: 2023-01-03 09:04

Resolved:: 2022-09-27 00:56

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates