found a post on builds mailing list with another example of this. That thread said:
Apparently, Pulsar jobs went wild. There are 14 processes which consume 9000+ threads Maybe they'll fix this... -Marshall On 1/17/2020 3:24 PM, Richard Eckart de Castilho wrote: > On 17. Jan 2020, at 21:10, Marshall Schor <[email protected]> wrote: >> java.lang.OutOfMemoryError: unable to create new native thread > Could be that too many Maven builds crashed/failed on that slave and caused > old Maven processes to hang around. There is a known bug for this on Jenkins > since ages. > > Exclude that build node from the Jenkins job to force Jenkins to build on > another node. > > You might also tell INFRA e.g. via Slack to check and maybe restart the slave. > > Cheers, > > -- Richard
