[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Integrated: 8265683: vmTestbase/nsk/jdb tests failed with "JDWP exit error AGENT_ERROR_INTERNAL(181)
From:       Chris Plummer <cjplummer () openjdk ! java ! net>
Date:       2021-04-22 23:30:27
Message-ID: hDADL_LBHd2mC5JVM2p7KeOC_PylPxkpsibuaybYP7o=.198b5ecd-eb9b-42f4-aa97-209eac2fe775 () github ! com
[Download RAW message or body]

On Thu, 22 Apr 2021 15:59:09 GMT, Chris Plummer <cjplummer@openjdk.org> wrote:

> This bug was introduced by my recent changes for \
> [JDK-8265028](https://bugs.openjdk.java.net/browse/JDK-8265028), which attempted to \
> speed up ThreadNode lookups by not looking in the runningThreads list if the TLS \
> lookup failed. At the time it was thought that the thread could not possibly be on \
> the list, but it turns out sometimes it can. 
> For now I'm just doing a quick fix to replace the assert being triggered with a \
> lookup instead, which is pretty much how it worked before JDK-8265028. However, I \
> eventually want to get back to not having to do the lookup, but first I need to \
> better understand why this is happening in the first place, and the tests are \
> failing too often to wait for that, thus the quick fix.

This pull request has now been integrated.

Changeset: a8ddbd15
Author:    Chris Plummer <cjplummer@openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/a8ddbd15
Stats:     9 lines in 1 file changed: 7 ins; 0 del; 2 mod

8265683: vmTestbase/nsk/jdb tests failed with "JDWP exit error \
AGENT_ERROR_INTERNAL(181)"

Reviewed-by: amenkov, dcubed

-------------

PR: https://git.openjdk.java.net/jdk/pull/3634


[prev in list] [next in list] [prev in thread] [next in thread]