[JIRA] [all-changes] (JENKINS-20759) On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll
boris ivan created JENKINS-20759 On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll Issue Type: Bug Affects Versions: current Assignee: wolfs Components: all-changes Created: 25/Nov/13 9:21 PM Description: Occasionally, remote windows slaves die with the following trace spit to the screen on the remote slave (I am running via command line, not as a service): Nov 20, 2013 4:16:10 PM org.jvnet.winp.Native load WARNING: Failed to write winp.x64.dll java.io.FileNotFoundException: C:\Users\\.jenkins\cache\jars\01\winp.x64.dll (The process can not access the file because it is being used by another process) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:212) at java.io.FileOutputStream.(FileOutputStream.java:165) at org.jvnet.winp.Native.load(Native.java:81) at org.jvnet.winp.Native.(Native.java:52) at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:200) at hudson.util.ProcessTree$Windows.(ProcessTree.java:477) at hudson.util.ProcessTree.get(ProcessTree.java:336) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:899) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:890) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:724) # A fatal error has been detected by the Java Runtime Environment: # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x0c8b3a90, pid=7136, tid=2024 # JRE version: 7.0_25-b17 Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode windows-amd64 compressed oops) Problematic frame: C 0x0c8b3a90 # Core dump written. Default location: C:hs_err_pid7136.mdmp # An error report file with more information is saved as: C:hs_err_pid7136.log When this occurs, here's the trailing end of the build console for this build: ... ... [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1:33.420s [INFO] Finished at: Wed Nov 20 16:16:09 EST 2013 [INFO] Final Memory: 42M/272M [INFO] [JENKINS] Archiving C:\jenkins\workspace\\pom.xml to SNAPSHOT.pom [JENKINS] Archiving C:\jenkins\workspace\-SNAPSHOT.jar to jar channel stopped FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:714) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1679) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketEx
[JIRA] [all-changes] (JENKINS-20759) On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll
boris ivan updated JENKINS-20759 On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll Change By: boris ivan (25/Nov/13 9:29 PM) Description: Occasionally, remote windows slaves die with the following trace spit to the screen on the remote slave (I am running via command line, not as a service): {noformat} Nov 20, 2013 4:16:10 PM org.jvnet.winp.Native loadWARNING: Failed to write winp.x64.dlljava.io.FileNotFoundException: C:\Users\\.jenkins\cache\jars\01\winp.x64.dll (The process can not access the file because it is being used by another process)at java.io.FileOutputStream.open(Native Method)at java.io.FileOutputStream.(FileOutputStream.java:212)at java.io.FileOutputStream.(FileOutputStream.java:165)at org.jvnet.winp.Native.load(Native.java:81)at org.jvnet.winp.Native.(Native.java:52)at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:200)at hudson.util.ProcessTree$Windows.(ProcessTree.java:477)at hudson.util.ProcessTree.get(ProcessTree.java:336)at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:899)at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:890)at hudson.remoting.UserRequest.perform(UserRequest.java:118)at hudson.remoting.UserRequest.perform(UserRequest.java:48)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)at java.util.concurrent.FutureTask.run(FutureTask.java:166)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at hudson.remoting.Engine$1$1.run(Engine.java:63)at java.lang.Thread.run(Thread.java:724)## A fatal error has been detected by the Java Runtime Environment:## EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x0c8b3a90, pid=7136, tid=2024## JRE version: 7.0_25-b17# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode windows-amd64 compressed oops)# Problematic frame:# C 0x0c8b3a90## Core dump written. Default location: C:\\hs_err_pid7136.mdmp## An error report file with more information is saved as:# C:\\hs_err_pid7136.log {noformat} When this occurs, here's the trailing end of the build console for this build: {noformat} ..[INFO] BUILD SUCCESS[INFO] [INFO] Total time: 1:33.420s[INFO] Finished at: Wed Nov 20 16:16:09 EST 2013[INFO] Final Memory: 42M/272M[INFO] [JENKINS] Archiving C:\jenkins\workspace\\pom.xml to SNAPSHOT.pom[JENKINS] Archiving C:\jenkins\workspace\-SNAPSHOT.jar to jarchannel stoppedFATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection resethudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:714) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1679) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230)Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:774) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)Caused by: java.net.SocketException: Connection reset at java.net
[JIRA] [all-changes] (JENKINS-20759) On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll
boris ivan updated JENKINS-20759 On windows slaves, occasional crash after successful build: Failed to write winp.x64.dll crashdump log file Change By: boris ivan (25/Nov/13 9:33 PM) Attachment: hs_err_pid7136.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.