Difference between revisions of "FAQ: How can I fix a "Cannot load Java Virtual Machine" error (memory limit set too high)?"
From MIPAV
m (moved How can I fix a "Cannot load Java Virtual Machine" error (memory limit set too high)? to FAQ: How can I fix a "Cannot load Java Virtual Machine" error (memory limit set too high)?: This is the FAQ page, so I moved it under the FAQ category) |
m |
||
Line 41: | Line 41: | ||
# Restart MIPAV. | # Restart MIPAV. | ||
# Try increasing the memory limit to something more reasonable, testing to make sure that MIPAV still starts after the change. | # Try increasing the memory limit to something more reasonable, testing to make sure that MIPAV still starts after the change. | ||
+ | |||
+ | |||
+ | == See also: == | ||
+ | *[[Getting Started Quickly with MIPAV]] | ||
+ | *[[Allocating Memory in MIPAV]] | ||
+ | *[[Opening and loading image files]] | ||
+ | |||
+ | Next: [[FAQ: Customizing MIPAV]] | ||
+ | |||
+ | [[Category: Help]] | ||
+ | |||
+ | [[Category: FAQ]] |
Revision as of 19:40, 13 June 2012
Sometimes MIPAV will not load if the memory limit is set too high (due to user error or another program -- like antivirus -- staying resident in memory). Usually the user will see an error saying something like "Cannot load Java Virtual Machine".
Windows/Linux
- Open the MIPAV LanuchAnywhere configuration file in a text editor:
- Windows example: C:\Program Files\mipav\mipav.lax
- Linux example: /path/to/mipav/mipav.lax
- Find the part of the file that resembles the below snippet (here the memory limit is ~1GB):
# LAX.NL.JAVA.OPTION.JAVA.HEAP.SIZE.INITIAL # ----------------------------------------- # Java start up heap size lax.nl.java.option.java.heap.size.initial=1000000000 # LAX.NL.JAVA.OPTION.JAVA.HEAP.SIZE.MAX # ------------------------------------- # Java maximum heap size lax.nl.java.option.java.heap.size.max=1000000000
- Change the number at the end of both property lines to a lower number (try 100000000 -- ~100MB to test).
- Restart MIPAV.
- Try increasing the memory limit to something more reasonable, testing to make sure that MIPAV still starts after the change.
MacOS X
- Open the MIPAV LanuchAnywhere configuration file in a text editor:
- Example: /Applications/mipav/mipav.app/Contents/Info.plist
- Find the part of the file that resembles the below snippet (here the memory limit is ~1GB):
<key>VMOptions</key> <array> <string>-Xms1000M</string> <string>-Xmx1000M</string> <string>-server</string> </array>
- Change the number in the lines containing the "-Xms" and "-Xmx" VM options to a lower number (try 100M to test).
- Restart MIPAV.
- Try increasing the memory limit to something more reasonable, testing to make sure that MIPAV still starts after the change.
See also:
Next: FAQ: Customizing MIPAV