After a recent Jenkins crash we have a number of jobs where the build history cannot load, and a Stack Overflow results.

Jenkins is running standalone, both behind an nginx reverse proxy (production) and not (test server, where the problem is reproducible with the same build histories).

The slave node of the problem jobs is running Ubuntu 12.04 64-bit.

The stack overflow error is attached.

Removing the bad builds resolves the problem.

Once the problem happens we do see other side effects, like nodes showing up as connected but jobs reporting that they are waiting for executors to be available when no builds are running.