I was able to get javadoc to fail (killed by the kernel oom-killer) by running another build at the same time. It was using about 2 GB of RAM at the time. Not good. I looked in the options file and there was no sign of anything setting the heap size (but then I am a javadoc n00b).
On 22/11/11 10:35, Michael Bedward wrote: > Mmm... that's approaching the "electron in p-orbital vs s-orbital" > level of detail. As a simple soul, I'd prefer a -DjustWork option. > > The fact that you are able to build the javadocs with -Xmx256m, while > Jody and I are failing with -Xmx2048m, suggests something is very > broken under OSX. > > Michael > > > On 22 November 2011 13:04, Ben Caradoc-Davies > <[email protected]> wrote: >> >> "Ordinary object pointer" >> http://wikis.sun.com/display/HotSpotInternals/CompressedOops >> http://blog.juma.me.uk/2008/10/14/32-bit-or-64-bit-jvm-how-about-a-hybrid/ >> >> The last page also claims that compressed oops are enabled by default in JDK >> 1.6.0_23 or later. A quick test with Eclipse suggests that this is indeed >> the case. >> > -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
