Heapspace Out of Memory Error

From 360Works Product Documentation Wiki
(Difference between revisions)
Jump to: navigation, search
(Windows:)
(Windows:)
Line 20: Line 20:
 
* On Windows Server 2008 the file should be 'C:\Users\Admin\360Works\memorysize'
 
* On Windows Server 2008 the file should be 'C:\Users\Admin\360Works\memorysize'
  
Create a blank text document and rename it to "memorysize". Enter the desired custom memory size in MB. There should only be numbers with no trailing spaces or carriage returns. You must ensure that the file has no extension (.txt, etc.). You can remove extensions by un-checking the "Hide extensions for known file types" box in Windows Explorer folder options. Then rename the file without the extension
+
Create a blank text document and rename it to "memorysize". Enter the desired custom memory size in MB. There should only be numbers with no trailing spaces or carriage returns. You must ensure that the file has no extension (.txt, etc.). You can remove extensions by un-checking the "Hide extensions for known file types" box in Windows Explorer folder options. Then rename the file without the extension. You may need to create the "360Works" directory.
  
 
You will need to restart FileMaker in order for the changes to take affect. You may need to restart the machine you make this change on after creating the memorysize file.
 
You will need to restart FileMaker in order for the changes to take affect. You may need to restart the machine you make this change on after creating the memorysize file.

Revision as of 16:37, 12 March 2014

By default, 360Works plugins use 96 MB of heap space for the JVM to run its code. When working with very large files or amounts of data, it is possible that a plugin may run out memory. To correct this you may need to adjust the memory that the plugin has available. NOTE: Values higher than 1024 MB can cause FMP/A to crash.

Mac:

  • create a file named memorysize with no extension at '/Library/Application Support/360FmKit/memorysize' which contains the required heap size, in megabytes (i.e. 128)

Instructions for using Terminal to create custom memorysize file

  • Open Terminal
  • Type "cd /Library/Application\ Support/360FmKit". If this directory doesn't exist yet, you will need to create it using either the "mkdir" command or through Finder
  • Type "sudo vi memorysize". You may be prompted for your password
  • Hit the "a" key to start "append" mode.
  • Enter the desired custom memory size in MB. There should only be the numbers with no trailing spaces or carriage returns.
  • Hit the "esc" key
  • Type ":wq" and hit return. ":" takes you into command mode, "w" is for "write", and "q" is for "quit" so this command will take you out of edit mode, save the file, and go back to the command prompt

Windows:

  • On Windows XP, the memorysize file should be located at 'C:\Documents and Settings\All Users\Application Data\360Works\memorysize'
  • On Windows Server 2008 the file should be 'C:\Users\Admin\360Works\memorysize'

Create a blank text document and rename it to "memorysize". Enter the desired custom memory size in MB. There should only be numbers with no trailing spaces or carriage returns. You must ensure that the file has no extension (.txt, etc.). You can remove extensions by un-checking the "Hide extensions for known file types" box in Windows Explorer folder options. Then rename the file without the extension. You may need to create the "360Works" directory.

You will need to restart FileMaker in order for the changes to take affect. You may need to restart the machine you make this change on after creating the memorysize file.

Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox