Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-3164

OS X builds on 1.285 always fail with a ProcessTreeKiller error

    • Icon: Bug Bug
    • Resolution: Postponed
    • Icon: Major Major
    • core
    • None
    • Platform: Macintosh, OS: All

      FATAL: Bounds exceeds available space : size=262144, offset=262145
      java.lang.IndexOutOfBoundsException: Bounds exceeds available space : size=262144, offset=262145
      at com.sun.jna.Memory.boundsCheck(Memory.java:149)
      at com.sun.jna.Memory.getByte(Memory.java:375)
      at hudson.util.ProcessTreeKiller$Darwin$DarwinProcess$1StringArrayMemory.skip0(ProcessTreeKiller.java:843)
      at hudson.util.ProcessTreeKiller$Darwin$DarwinProcess.parse(ProcessTreeKiller.java:896)
      at hudson.util.ProcessTreeKiller$Darwin$DarwinProcess.getEnvVars(ProcessTreeKiller.java:786)
      at hudson.util.ProcessTreeKiller$Unix.kill(ProcessTreeKiller.java:243)
      at hudson.util.ProcessTreeKiller.kill(ProcessTreeKiller.java:109)
      at hudson.Launcher$LocalLauncher.kill(Launcher.java:361)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:275)
      at hudson.model.Run.run(Run.java:894)
      at hudson.model.Build.run(Build.java:112)
      at hudson.model.ResourceController.execute(ResourceController.java:93)
      at hudson.model.Executor.run(Executor.java:119)

          [JENKINS-3164] OS X builds on 1.285 always fail with a ProcessTreeKiller error

          mschrag added a comment -

          emerald:~ root# uname -a
          Darwin emerald.hq.mdimension.com 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT
          2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386

          it's a Tiger Server box ...

          mschrag added a comment - emerald:~ root# uname -a Darwin emerald.hq.mdimension.com 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 it's a Tiger Server box ...

          jbrook added a comment -

          I have the same error on Leopard server running on a recent XServe: uname -a
          Darwin vaca 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-
          1228.7.58~1/RELEASE_I386 i386

          BUILD SUCCESSFUL
          Total time: 14 minutes 18 seconds
          [workspace] $ /bin/sh -xe /tmp/hudson57118.sh
          + ps auxww
          + grep CMS
          + grep java
          + awk '

          {print $2}'
          + xargs kill
          [workspace] $ /bin/sh -xe /tmp/hudson57119.sh
          + ps auxww
          + grep java
          + grep PortalUpdate
          + awk '{print $2}

          '
          + xargs kill
          FATAL: Bounds exceeds available space : size=262144, offset=262145
          java.lang.IndexOutOfBoundsException: Bounds exceeds available space : size=262144, offset=262145
          at com.sun.jna.Memory.boundsCheck(Memory.java:149)
          at com.sun.jna.Memory.getByte(Memory.java:375)
          at
          hudson.util.ProcessTreeKiller$Darwin$DarwinProcess$1StringArrayMemory.skip0(ProcessTreeKiller.java:
          846)
          at hudson.util.ProcessTreeKiller$Darwin$DarwinProcess.parse(ProcessTreeKiller.java:899)
          at hudson.util.ProcessTreeKiller$Darwin$DarwinProcess.getEnvVars(ProcessTreeKiller.java:789)
          at hudson.util.ProcessTreeKiller$Unix.kill(ProcessTreeKiller.java:246)
          at hudson.util.ProcessTreeKiller.kill(ProcessTreeKiller.java:109)
          at hudson.Launcher$LocalLauncher.kill(Launcher.java:377)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:277)
          at hudson.model.Run.run(Run.java:895)
          at hudson.model.Build.run(Build.java:112)
          at hudson.model.ResourceController.execute(ResourceController.java:93)
          at hudson.model.Executor.run(Executor.java:119)

          jbrook added a comment - I have the same error on Leopard server running on a recent XServe: uname -a Darwin vaca 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu- 1228.7.58~1/RELEASE_I386 i386 BUILD SUCCESSFUL Total time: 14 minutes 18 seconds [workspace] $ /bin/sh -xe /tmp/hudson57118.sh + ps auxww + grep CMS + grep java + awk ' {print $2}' + xargs kill [workspace] $ /bin/sh -xe /tmp/hudson57119.sh + ps auxww + grep java + grep PortalUpdate + awk '{print $2} ' + xargs kill FATAL: Bounds exceeds available space : size=262144, offset=262145 java.lang.IndexOutOfBoundsException: Bounds exceeds available space : size=262144, offset=262145 at com.sun.jna.Memory.boundsCheck(Memory.java:149) at com.sun.jna.Memory.getByte(Memory.java:375) at hudson.util.ProcessTreeKiller$Darwin$DarwinProcess$1StringArrayMemory.skip0(ProcessTreeKiller.java: 846) at hudson.util.ProcessTreeKiller$Darwin$DarwinProcess.parse(ProcessTreeKiller.java:899) at hudson.util.ProcessTreeKiller$Darwin$DarwinProcess.getEnvVars(ProcessTreeKiller.java:789) at hudson.util.ProcessTreeKiller$Unix.kill(ProcessTreeKiller.java:246) at hudson.util.ProcessTreeKiller.kill(ProcessTreeKiller.java:109) at hudson.Launcher$LocalLauncher.kill(Launcher.java:377) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:277) at hudson.model.Run.run(Run.java:895) at hudson.model.Build.run(Build.java:112) at hudson.model.ResourceController.execute(ResourceController.java:93) at hudson.model.Executor.run(Executor.java:119)

          jbrook added a comment -

          I still haven't found a resolution or workaround for this issue. I am running 1.300 now and my builds still
          don't work. Is there any more information I can provide.

          Is it safe to roll back to an older version of hudson?

          jbrook added a comment - I still haven't found a resolution or workaround for this issue. I am running 1.300 now and my builds still don't work. Is there any more information I can provide. Is it safe to roll back to an older version of hudson?

          yusuke added a comment -

          I have a same issue on my iBook - Leopard 10.5.6 with ver. 1.293.

          $ uname -a
          Darwin yusuke-homeip-net.local 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:39:01 PST 2008;
          root:xnu-1228.9.59~1/RELEASE_PPC Power Macintosh

          You can see the full stacktrace below.
          http://yusuke.homeip.net/hudson/job/Twitter4J/39/console

          yusuke added a comment - I have a same issue on my iBook - Leopard 10.5.6 with ver. 1.293. $ uname -a Darwin yusuke-homeip-net.local 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:39:01 PST 2008; root:xnu-1228.9.59~1/RELEASE_PPC Power Macintosh You can see the full stacktrace below. http://yusuke.homeip.net/hudson/job/Twitter4J/39/console

          jbrook added a comment -

          I managed to work around my issue by disabling the ProcessTreeKiller functionality in Hudson. It is
          something that tries, at the end of the build, to cleanly deal with killing processes that the build has
          started. It can be disabled with a system property when staring up hudson:

          -Dhudson.util.ProcessTreeKiller.disable=true

          jbrook added a comment - I managed to work around my issue by disabling the ProcessTreeKiller functionality in Hudson. It is something that tries, at the end of the build, to cleanly deal with killing processes that the build has started. It can be disabled with a system property when staring up hudson: -Dhudson.util.ProcessTreeKiller.disable=true

          Alan Harder added a comment -

          ProcessTreeKiller was refactored into just "ProcessTree" in 1.315.. perhaps
          these problems were resolved in the process? Can someone report back if this
          issue still exists on the latest Hudson release?

          Alan Harder added a comment - ProcessTreeKiller was refactored into just "ProcessTree" in 1.315.. perhaps these problems were resolved in the process? Can someone report back if this issue still exists on the latest Hudson release?

          yusuke added a comment -

          I've been using ver. 1.328 for a month with -Dhudson.util.ProcessTreeKiller.disable=true without any
          problem.
          If "ProcessTree" doesn't recognize hudson.util.ProcessTreeKiller.disable prop, we could mark this issue
          as resolved.

          My environment info are:
          $ uname -a
          Darwin yusuke-homeip-net.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009;
          root:xnu-1228.15.4~1/RELEASE_PPC Power Macintosh
          $ java -version
          java version "1.5.0_20"
          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_20-b02-315)
          Java HotSpot(TM) Client VM (build 1.5.0_20-141, mixed mode, sharing)

          Thanks,
          Yusuke

          yusuke added a comment - I've been using ver. 1.328 for a month with -Dhudson.util.ProcessTreeKiller.disable=true without any problem. If "ProcessTree" doesn't recognize hudson.util.ProcessTreeKiller.disable prop, we could mark this issue as resolved. My environment info are: $ uname -a Darwin yusuke-homeip-net.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC Power Macintosh $ java -version java version "1.5.0_20" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_20-b02-315) Java HotSpot(TM) Client VM (build 1.5.0_20-141, mixed mode, sharing) Thanks, Yusuke

          Alan Harder added a comment -

          yusuke, thanks for the reply.. ProcessTree does recognize both the old and new
          names, so you are currently NOT using ProcessTree to cleanup processes.

          Alan Harder added a comment - yusuke, thanks for the reply.. ProcessTree does recognize both the old and new names, so you are currently NOT using ProcessTree to cleanup processes.

          Alan Harder added a comment -

          Can someone test on recent Hudson without the system property to disable ProcessTree and report the results? Thanks.

          Alan Harder added a comment - Can someone test on recent Hudson without the system property to disable ProcessTree and report the results? Thanks.

          Alan Harder added a comment -

          Will close soon without further input, thanks.

          Alan Harder added a comment - Will close soon without further input, thanks.

            Unassigned Unassigned
            mschrag mschrag
            Votes:
            4 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: