On Mon, 25 Sep 2023 16:16:51 GMT, Roman Kennke <rken...@openjdk.org> wrote:
> The SA can run concurrently with Java threads, SA code that inspects locking > state should be able to deal with that. On the other hand, the particular > code is only used in printing routine and is not expected to be precise. When > resolving an anonymous owner, we may not find one, because Java threads may > already have moved on. Instead of crashing with a stacktrace, we should > gracefully return null here. > > Testing: > - [x] sun/tools/jhsdb/JStackStressTest.java > - [x] sun/tools/jhsdb > - [x] serviceability/sa This pull request has now been integrated. Changeset: bd918f49 Author: Roman Kennke <rken...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/bd918f49d29bcbc699e07b4ef8d23cfe1abd32df Stats: 5 lines in 1 file changed: 4 ins; 0 del; 1 mod 8316401: sun/tools/jhsdb/JStackStressTest.java failed with "InternalError: We should have found a thread that owns the anonymous lock" Reviewed-by: cjplummer, dholmes ------------- PR: https://git.openjdk.org/jdk/pull/15907
