Some of our projects have symlinks that reference other folders within the workspace. When we specify artifacts to archive from such a workspace, Hudson goes into a tail spin where it's consuming around 100% of a processor core until it runs out of memory and all builds start failing.

I used the fs_usage tool and it looks like Hudson is doing "stat" operations on files throughout the workspace. My suspicion is that when Hudson hits a symlink it recurses until it runs out of memory, but this is just a theory; I admit that I haven't looked at the code.

The only work around has been for us to copy the deliverables to another job's workspace (one without any symlinks), then trigger that job to gather up the artifacts. This is very ugly and requires build machine affinity between jobs.

We've got Hudson version 1.341 installed, but I don't see any indication from the change log that this problem has been addressed.