Status: Resolved (View Workflow)
Jenkins 2.7.4 installed via RPM
Oracle JDK 1.8.0_102-b14
CentOS release 6.5 (Final) VM
I've been experiencing crashes of the Jenkins master approximately once a month for the last several months. In every case, a core dump is generated that references "com.trilead.ssh2.crypto" and a similar message (dumps attached). I've been unable to reproduce with a simple installation as I'm struggling to track down any single activity that could be the cause. Let me know if a list of installed plugins would be helpful.
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f02d76c7bf1, pid=19717, tid=0x00007f0235a59700 # # JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode linux-amd64 compressed oops) # Problematic frame: # J 13231 C2 com.trilead.ssh2.crypto.digest.MD5.transform([BI)V (1563 bytes) @ 0x00007f02d76c7bf1 [0x00007f02d76c6e60+0xd91] # # Core dump written. Default location: //core or core.19717 # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp #
- is duplicated by
JENKINS-44181 Master crash with SEGV on copyartifact, caused by com.trilead.ssh2.crypto
Are you able to provide the core dump that goes alongside the attached logs?
Code changed in jenkins
User: Michael Clarke
Bump Trilead version to receive a number of security enhancements
JENKINS-41606 JENKINS-33021 JENKINS-26379 JENKINS-31549
I just opened a possibly similar issue: https://issues.jenkins-ci.org/browse/JENKINS-51047
it should be resolved now, the library uses the JDK MD5 implementation
I wish we could get rid of trilead at all. CC rsandell