search

timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-66973] Memory corruption when switching to OpenJ9 #1700

Closed timja closed 2 years ago

timja commented 3 years ago

When we were trying to switch Java from Hotspot to OpenJ9 machine, OpenJ9 terminates with Memory corruption as soon as one signs into Jenkins. This the stderr output ( apologies for german)::

06:30:03.765 0x24ec400 omrport.359 * ** ASSERTION FAILED ** at C:\workspace\openjdk-build\workspace\build\src\omr\port\common\omrmemtag.c:145: ((memoryCorruptionDetected))
JVMDUMP039I Speicherauszugsereignis "traceassert", Detail "" um 2021/09/27 08:30:03 - bitte warten.
JVMDUMP032I JVM forderte als Antwort auf ein Ereignis einen Speicherauszug von System mit "c:\jenkins\core.20210927.083003.49288.0001.dmp" an
JVMDUMP010I Speicherauszug von System in c:\jenkins\core.20210927.083003.49288.0001.dmp geschrieben
JVMDUMP032I JVM forderte als Antwort auf ein Ereignis einen Speicherauszug von Java mit "c:\jenkins\javacore.20210927.083003.49288.0002.txt" an

 

More details of analysis might be found in issue created for openj9 here:

https://github.com/eclipse-openj9/openj9/issues/13570

 

Originally reported by amesser, imported from: Memory corruption when switching to OpenJ9
  • status: Closed
  • priority: Major
  • resolution: Won't Fix
  • resolved: 2021-11-22T05:54:59+00:00
  • imported: 2022/01/10
timja commented 3 years ago

markewaite:

The platform SIG has stopped its work on OpenJ9 for Jenkins. There were not enough volunteers interested in testing or maintaining OpenJ9 so we removed OpenJ9 support from the roadmap and from the Docker images.

We don't take any active measures to prevent Jenkins from running with OpenJ9, but we also do not have many users that are running with OpenJ9 and none of the Docker image maintainers were willing to spend time on OpenJ9. You're welcome to submit bug reports of issues and pull requests proposing improvements and fixes for OpenJ9 use cases.

timja commented 2 years ago

amesser:

Thanks for getting back to me. I have discuss internally how we proceed.

timja commented 2 years ago

markewaite:

Since we're not doing any work to test OpenJ9 or maintain runtime on it, I'm closing this issue report.