Morty, thanks for tracking down that information. You're right, I have 8GB of RAM on my local machine.
So if the problem is that the ulimit is lower than 1/4 of the total memory reported, then does adding more memory makes things worse, not better? In any case, I think you're right that having the launchpad build scripts set _JAVA_OPTIONS="-Xmx****" for **** to be determined would seem sensible. I'd vote for more than 64m as I'm reasonable sure we'll have packages that won't build in that, but something like 256m should be enough I suppose.
It's a shame that there are problems installing dependencies (e.g. setting up openjdk-6-jre-headless itself) otherwise this could be fixed just in the debian/rules file. In any case I'll add it to my debian/rules and see if that helps matters.
Morty, thanks for tracking down that information. You're right, I have 8GB of RAM on my local machine.
So if the problem is that the ulimit is lower than 1/4 of the total memory reported, then does adding more memory makes things worse, not better? In any case, I think you're right that having the launchpad build scripts set _JAVA_OPTIONS= "-Xmx** **" for **** to be determined would seem sensible. I'd vote for more than 64m as I'm reasonable sure we'll have packages that won't build in that, but something like 256m should be enough I suppose.
It's a shame that there are problems installing dependencies (e.g. setting up openjdk- 6-jre-headless itself) otherwise this could be fixed just in the debian/rules file. In any case I'll add it to my debian/rules and see if that helps matters.