-
Bug
-
Resolution: Unresolved
-
Major
-
EC2 Plugin 1.31
Jenkins 1.625.16.1
A Jenkins master running the EC2 Plugin will exhibit high CPU usage. High CPU Analysis will show threads with a stack trace similar to:
"input copy: java -jar C:\Windows\Temp\slave.jar" #53906 daemon prio=5 os_prio=0 tid=0x00007fab61963800 nid=0x1860 runnable [0x00007fab1288f000] java.lang.Thread.State: RUNNABLE at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:783) - locked <0x00000006b9e757f8> (a java.io.IOException) at java.lang.Throwable.<init>(Throwable.java:265) at java.lang.Exception.<init>(Exception.java:66) at java.io.IOException.<init>(IOException.java:58) at java.io.PipedInputStream.read(PipedInputStream.java:310) - locked <0x00000005583223c0> (a java.io.PipedInputStream) at java.io.PipedInputStream.read(PipedInputStream.java:377) - locked <0x00000005583223c0> (a java.io.PipedInputStream) at java.io.InputStream.read(InputStream.java:101) at hudson.plugins.ec2.win.winrm.WindowsProcess$2.run(WindowsProcess.java:124)
Which appears to be related to this code in the EC2 plugin.
Running jvmtop with --profile option gave me this analysis:
During the analysis I did not have any ec2 windows agents running so this seems a bit weird. Running Jenkins 2.32.1 and EC2 plugin 1.36.