sanity.system_x86-64_windows TestJlmRemoteMemoryNoAuth_0 crash vmState=0x0002000f #7156
Labels
Milestone
Comments
|
Bad o-slot pointer in Bytecode frame:
|
|
That O-Slot is an argument to the method and should be a MethodHandle object. Do you have the caller's frame as well? |
|
|
you can find system core in my team folder under 7156/ |
|
It looks like the bad value @andrewcraik Can you have someone take a look at this? |
|
@liqunl this looks like it could be a handle problem - could you have a look? |
|
Given this has only happened once in the nightly builds, seems unlikely to be fixed in the 0.17 release, except maybe under a different issue. Moving this one to the next release. Note there was another issue for the same vmstate, but it was closed for lack of reproduction. #5764 |
pshipton
modified the milestones:
Release 0.17 (Java 8, 11, 13) Oct refresh,
Release 0.18 (Java 8, 11, 13) Jan refresh
|
@andrewcraik I haven't been able to reproduce the failure, no progress has been made so far. |
|
Closing until the problem is seen again. |
mpirvu
added a commit
to mpirvu/openj9
that referenced
this issue
Oct 27, 2023
By default, OpenJ9 uses an "implicit" shared class cache (SCC) that is used to cache "bootstrap" classes and methods. Currently, methods whose class is not present in the SCC receive a high initial invocation count (3000/3000 for loopless/loopy method) in order to improve steady state throughput. However, this could affect start-up time of applications because methods are interpreted for too long before being JIT compiled. The presence of `-Xshareclasses` on the command line is a sign that the user cares about start-up time and OpenJ9 automatically lowers the invocations counts to 1000/250. However, with the implicit SCC (no -Xshareclasses command line option), application classes are not cached and methods belonging to those classes will receive a large initial invocation count (3000/3000). Since application classes are likely important, we would like to use lower counts even when the implict SCC is used. This commit lowers the initial invocation counts for methods whose class is not in SCC under the following conditions: - SCC is used. Rationale: -Xshareclasses:none may be a sign that user does not care about start-up that much. - -Xtune:throughput is not used. Rationale: this option is a clear signal that the user cares more about throughput than startup. - The user has not provided a specific count on the command line. - The JVM is in start-up mode. Rationale: this feature only seeks to improve start-up time. - The JVM runs on 4 or more vCPUs. Rationale: lower counts will generate more compilations which will compete with application Depends on eclipse/omr/eclipse-openj9#7156 Signed-off-by: Marius <mpirvu@ca.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://ci.eclipse.org/openj9/job/Test_openjdk13_j9_sanity.system_x86-64_windows_Nightly/43
TestJlmRemoteMemoryNoAuth_0
core file in the artifacts https://140-211-168-230-openstack.osuosl.org/artifactory/ci-eclipse-openj9/Test/Test_openjdk13_j9_sanity.system_x86-64_windows_Nightly/43/system_test_output.tar.gz
The text was updated successfully, but these errors were encountered: