I managed to program my pipeline library so that it leads to the Jenkins job eating up all CPU, OOMing and successfully still surviving any restarts or requests to stop the job.
The following Jenkins file should help you to reproduce this:
This code here defines a method setKitchenLocalYmlName() which matches the synthetic accessor's name of the kitchenLocalYmlName class variable (a thing, of which I wasn't aware of).
This seems to be something that Jenkins cannot handle. Renaming the method or variable solves the problem.
The error occurs immediately after checking out the code (I thought it was during git ref-list parsing, that's why the branch is called like this).