Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Not A Defect
-
Component/s: trilead-api-plugin
-
Labels:None
-
Environment:Jenkins 2.89.4
JRE version: OpenJDK Runtime Environment (8.0_161-b14) (build 1.8.0_161-b14)
Java VM: OpenJDK 64-Bit Server VM (25.161-b14 mixed mode linux-amd64 compressed oops)
running in an AWS EC2 instance
-
Similar Issues:
Description
Over the last couple months we have seen an uptick in Jenkins JVM crashes that seem to be related to Trilead. Here are three stack traces from crash logs:
Stack: [0x00007f5597b23000,0x00007f5597c24000], sp=0x00007f5597c22550, free space=1021k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) J 14468 C2 sun.security.provider.SHA5.implCompress([BI)V (331 bytes) @ 0x00007f55ea496341 [0x00007f55ea496060+0x2e1] J 18715 C2 sun.security.provider.DigestBase.engineUpdate([BII)V (189 bytes) @ 0x00007f55eb87cba8 [0x00007f55eb87c9c0+0x1e8] J 48093 C2 com.trilead.ssh2.transport.TransportConnection.receiveMessage([BII)I (470 bytes) @ 0x00007f55f0bc7fd4 [0x00007f55f0bc6e20+0x11b4] J 45325% C2 com.trilead.ssh2.transport.TransportManager.receiveLoop()V (549 bytes) @ 0x00007f55eddc2d78 [0x00007f55eddc2ca0+0xd8] j com.trilead.ssh2.transport.TransportManager$1.run()V+4 j java.lang.Thread.run()V+11 v ~StubRoutines::call_stub V [libjvm.so+0x65b9cb] V [libjvm.so+0x65cde7] V [libjvm.so+0x65d2a7] V [libjvm.so+0x6ac811] V [libjvm.so+0x9ebea5] V [libjvm.so+0x9ec168] V [libjvm.so+0x8ada22] C [libpthread.so.0+0x7aa1]
Stack: [0x00007fd9c44fe000,0x00007fd9c45ff000], sp=0x00007fd9c45fd420, free space=1021k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) J 54733 C2 sun.security.provider.SHA5.implCompress([BI)V (331 bytes) @ 0x00007fda5ab045d1 [0x00007fda5ab042e0+0x2f1] J 14183 C2 sun.security.provider.DigestBase.engineUpdate([BII)V (189 bytes) @ 0x00007fda5b693868 [0x00007fda5b693680+0x1e8] J 14308 C2 com.sun.crypto.provider.HmacCore.engineUpdate([BII)V (35 bytes) @ 0x00007fda5a0a57a8 [0x00007fda5a0a5700+0xa8] J 39077 C2 com.trilead.ssh2.transport.TransportConnection.receiveMessage([BII)I (470 bytes) @ 0x00007fda6015c9c4 [0x00007fda6015c2a0+0x724] J 39111 C2 com.trilead.ssh2.transport.TransportManager.receiveLoop()V (549 bytes) @ 0x00007fda5b60e4a8 [0x00007fda5b60e3e0+0xc8] j com.trilead.ssh2.transport.TransportManager$1.run()V+4 J 33677 C2 java.lang.Thread.run()V (17 bytes) @ 0x00007fda5c4b45ac [0x00007fda5c4b4560+0x4c] v ~StubRoutines::call_stub V [libjvm.so+0x65cfeb] V [libjvm.so+0x65e407] V [libjvm.so+0x65e8c7] V [libjvm.so+0x6adee1] V [libjvm.so+0x9efc95] V [libjvm.so+0x9eff58] V [libjvm.so+0x8afe72] C [libpthread.so.0+0x7aa1]
Stack: [0x00007f850f8d4000,0x00007f850f9d5000], sp=0x00007f850f9d34a0, free space=1021k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) J 92379 C2 com.trilead.ssh2.crypto.cipher.AES.encryptBlock([[I)V (1195 bytes) @ 0x00007f85a58fe67d [0x00007f85a58fe340+0x33d] J 13649 C2 com.trilead.ssh2.crypto.cipher.AES.processBlock([BI[BI)I (111 bytes) @ 0x00007f85a666f9a8 [0x00007f85a666f800+0x1a8] J 13612 C2 com.trilead.ssh2.crypto.cipher.CipherInputStream.read([BII)I (90 bytes) @ 0x00007f85a6a07fe0 [0x00007f85a6a07e40+0x1a0] J 29255 C2 com.trilead.ssh2.transport.TransportConnection.receiveMessage([BII)I (470 bytes) @ 0x00007f85a9f46984 [0x00007f85a9f46860+0x124] J 45867% C2 com.trilead.ssh2.transport.TransportManager.receiveLoop()V (549 bytes) @ 0x00007f85ad1df190 [0x00007f85ad1df0a0+0xf0] j com.trilead.ssh2.transport.TransportManager$1.run()V+4 j java.lang.Thread.run()V+11 v ~StubRoutines::call_stub V [libjvm.so+0x65cfeb] V [libjvm.so+0x65e407] V [libjvm.so+0x65e8c7] V [libjvm.so+0x6adee1] V [libjvm.so+0x9efc95] V [libjvm.so+0x9eff58] V [libjvm.so+0x8afe72] C [libpthread.so.0+0x7aa1]
I realize this is not a ton of help for reproducing the problem. If you think I should file an OpenJDK bug report instead, please let me know.
Thanks!
Attachments
Activity
the two first errors happen on JDK classes on bits manipulation operations, the third happens on the trilead library also on bits manipulation operations. So errors happen in different places with different code but with similar purposes. I would say is not related to the Trilead library neither Jenkins. There is no more reports of similar issues in about 2 years, nobody is watching this issue nor vote for it, so I think we can close it.
See also https://issues.jenkins-ci.org/browse/JENKINS-41606