Difference between revisions of "Autopsy 3 Troubleshooting"

From SleuthKitWiki
Jump to: navigation, search
m
m
Line 1: Line 1:
1. Autopsy start issues.
+
1. Autopsy launch issues.
  
* "JVM creation failed" pop up dialog shown when launch Autopsy.
+
* "JVM creation failed" pop up dialog shown when launching Autopsy.
  
 
Cause: JVM is not able to allocate the requested 768m for heap size due to more memory requiring to load other native resources.
 
Cause: JVM is not able to allocate the requested 768m for heap size due to more memory requiring to load other native resources.

Revision as of 12:38, 25 April 2013

1. Autopsy launch issues.

  • "JVM creation failed" pop up dialog shown when launching Autopsy.

Cause: JVM is not able to allocate the requested 768m for heap size due to more memory requiring to load other native resources.

Solution: reduce amount of memory allocated to jvm:

as Administrator, edit the file: C:\Program Files (x86)\Autopsy\etc\autopsy.conf

and change the line:

default_options="--branding autopsy -J-Xms24m -J-Xmx768m -J-XX:MaxPermSize=256M -J Xverify:none"

to something like:

default_options="--branding autopsy -J-Xms24m -J-Xmx512m -J-XX:MaxPermSize=128M -J-Xverify:none"

save the file, and restart Autopsy.

If that didn't work, change the line to:

default_options="--branding autopsy"

  • Autopsy crashes after start when running within Virtual Machine, such as VMWare Fusion:

Cause: Incompatibility between some virtual machine video drivers and java.

Solution: shut down the virtual machine, disable Video Acceleration (both 2D and 3D if available) in the virtual machine settings, restart the virtual machine, restart Autopsy.