Skip to content

Conversation

@wendigo
Copy link
Contributor

@wendigo wendigo commented Mar 26, 2024

@wendigo wendigo requested a review from findepi March 26, 2024 11:02
@cla-bot cla-bot bot added the cla-signed label Mar 26, 2024
@wendigo wendigo requested a review from nineinchnick March 26, 2024 11:02
@wendigo wendigo requested a review from losipiuk March 26, 2024 11:20
@wendigo
Copy link
Contributor Author

wendigo commented Mar 26, 2024

This is new:

#  SIGSEGV (0xb) at pc=0x00007f14fa61fcd1, pid=2495, tid=2628
#
# JRE version: OpenJDK Runtime Environment Temurin-22+36 (22.0+36) (build 22+36)
# Java VM: OpenJDK 64-Bit Server VM Temurin-22+36 (22+36, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x81fcd1][thread 2610 also had an error]
  G1ParScanThreadState::trim_queue_to_threshold(unsigned int)+0x3861

adoptium/adoptium-support#959

@wendigo wendigo merged commit 7f636db into trinodb:master Mar 26, 2024
@github-actions github-actions bot added this to the 444 milestone Mar 26, 2024
@wendigo wendigo deleted the serafin/rpm-errorprone branch March 26, 2024 12:05
@findepi
Copy link
Member

findepi commented Mar 27, 2024

JRE version: OpenJDK Runtime Environment Temurin-22+36 (22.0+36) (build 22+36)

is this related to #21161?

@wendigo
Copy link
Contributor Author

wendigo commented Mar 27, 2024

@findepi rather to the reduced memory than to a jdk 22

@findepi
Copy link
Member

findepi commented Mar 27, 2024

might be, agreed! but did we reduce memory for maven main process or for tests (#21256)?
BTW it says SIGSEGV rather than "out of memory".

@wendigo
Copy link
Contributor Author

wendigo commented Mar 27, 2024

@findepi the linked bug manifests itself during high-memory pressure scenarios hence the assumption. Let's monitor this

@findepi
Copy link
Member

findepi commented Mar 28, 2024

not sure which part of the linked bug (adoptium/adoptium-support#959) apply to our case. it says Java 21 but it also says it's resolved for some time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

4 participants