-
Bug
-
Resolution: Unresolved
-
Critical
Post build task recently started to generate exception, while it was working great before (upgrade to jenkins 1.449 or 1.450).
Here is the exception trace. It occurs right after "Archiving artifacts"
FATAL: Java heap space
09:36:53 java.lang.OutOfMemoryError: Java heap space
09:36:53 at java.lang.AbstractStringBuilder.<init>(AbstractStringBuilder.java:62)
09:36:53 at java.lang.StringBuilder.<init>(StringBuilder.java:97)
09:36:53 at hudson.Util.loadFile(Util.java:171)
09:36:53 at hudson.model.Run.getLog(Run.java:1562)
09:36:53 at hudson.plugins.postbuildtask.PostbuildTask.perform(PostbuildTask.java:99)
09:36:53 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
09:36:53 at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:700)
09:36:53 at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:675)
09:36:53 at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:653)
09:36:53 at hudson.model.Build$RunnerImpl.post2(Build.java:162)
09:36:53 at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:622)
09:36:53 at hudson.model.Run.run(Run.java:1434)
09:36:53 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
09:36:53 at hudson.model.ResourceController.execute(ResourceController.java:88)
09:36:53 at hudson.model.Executor.run(Executor.java:238)
Is it reproduced with a recent Jenkins version?
If yes, would it be ok to just increase -Xmx in your configuration?
(Without more information on your server and on your jobs, it will be hard to know the cause of this. And yes, your current jobs/builds or perhaps new jenkins version may need just a little bit more heap memory than before and that is not always a defect. It depends on what you do with this server.)