Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
On 64bit Windows, 32bit processes run in wow64 translation layer. These processes have a different memory layout, which prevents winp from correctly finding all the processes executed in a context of a build and killing them.
We need to improve 64bit version of winp so that it can correctly recognize wow64 processes and list up their environment variables, so that Jenkins can kill them.
Attachments
Activity
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/pom.xml
http://jenkins-ci.org/commit/jenkins/6b9c4ee6e8905a6eb701a95fcca63559e6bf2fa1
Log:
[FIXED JENKINS-23410]
Integrated the fix made in winp 1.20.
(cherry picked from commit fad3f7db48e4184221469fbbb0edc2163e26ac0f)
Classifying as bug to make it eligible for LTS inclusion. Might still be rejected, but at least it won't be filtered by default 
While this change is an improvement over the previous situation, the previous limitation of not being able to kill a subset of processes that happens to run in wow64 is not distinguishable from a bug.
Integrated in 
jenkins_main_trunk #3463
[FIXED JENKINS-23410] (Revision fad3f7db48e4184221469fbbb0edc2163e26ac0f)
Result = SUCCESS
kohsuke : fad3f7db48e4184221469fbbb0edc2163e26ac0f
Files :
- core/pom.xml
- changelog.html
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/pom.xml
http://jenkins-ci.org/commit/jenkins/fad3f7db48e4184221469fbbb0edc2163e26ac0f
Log:
[FIXED JENKINS-23410]
Integrated the fix made in winp 1.20.
Thanks so much for resolving this issue! Just happened to see it in the changelog, and was reminded of being badly bitten by it in the past. (I'd always assumed that it was just a bug in our code.)