turns out we have been distributing the mac version of gridoworks with the default JVM max_heap settings... no wonder why so many people were getting OutOfMemory errors
git-svn-id: http://google-refine.googlecode.com/svn/trunk@439 7d457c2a-affb-35e4-300a-418c747d4874
This commit is contained in:
parent
70449cf7c8
commit
924f520fbf
@ -117,7 +117,7 @@
|
|||||||
workingdirectory="$APP_PACKAGE/Contents/Resources"
|
workingdirectory="$APP_PACKAGE/Contents/Resources"
|
||||||
jvmversion="1.6+"
|
jvmversion="1.6+"
|
||||||
bundleid="com.metaweb.gridworks.Gridworks"
|
bundleid="com.metaweb.gridworks.Gridworks"
|
||||||
vmoptions="-Dgridworks.version=${revision} ${java.options}"
|
vmoptions="-Xms256M -Xmx1024M -Dgridworks.version=${revision}"
|
||||||
antialiasedgraphics="true"
|
antialiasedgraphics="true"
|
||||||
antialiasedtext="true"
|
antialiasedtext="true"
|
||||||
liveresize="true"
|
liveresize="true"
|
||||||
|
Loading…
Reference in New Issue
Block a user