This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | NetBeans Crashes when running (any kind of) module suite | ||
---|---|---|---|
Product: | platform | Reporter: | stefika |
Component: | JDK Problems | Assignee: | issues@platform <issues> |
Status: | CLOSED INVALID | ||
Severity: | normal | ||
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | Macintosh (x86) | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | The module suite |
Description
stefika
2010-06-30 15:07:01 UTC
-Xmx is useless if you are getting PermGen OOMEs; you need to use -XX:MaxPermSize. If there is a segmentation fault rather than an OOME, that may be a bug in Apple's JDK port. Crud, you're right, sorry to waste your time, Jesse. When I change our script to include the flags you mentioned: <target name="build-launchers" depends="suite.build-launchers"> <echo message="Updating conf defaults for branding"/> <propertyfile file="${build.launcher.dir}/etc/${app.name}.conf"> <entry key="default_options" value='"--branding ${branding.token} --J-client -J-Xss2m -J-Xms32m -J-XX:PermSize=32m -J-XX:MaxPermSize=1024m"'/> <entry key="default_userdir" value='"${HOME}/.${app.name}/dev"'/> <entry key="default_mac_userdir" value='"${HOME}/Library/Application Support/.${app.name}/dev"'/> </propertyfile> </target> And I generate a zip file, it does indeed work correctly, although, oddly, it puts slashes in each of the flags, like so: default_options="--branding crashtest --J-client -J-Xss2m -J-Xms32m -J-XX\:PermSize\=32m -J-XX\:MaxPermSize\=1024m" It still seems to work with the slashes in there, but I'm not sure if they matter, and the default netbeans.conf file has no slashes. Those flags still don't seem to work when running the code in the debugger, however, and the PERMGEN errors still persist. Perhaps that's a problem with my ant script, although it isn't obvious to me why that would be. v/c |