-
Notifications
You must be signed in to change notification settings - Fork 595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX: Autopsy 3.0.8 Java "Cannot create Java Virtual Machine" #379
Comments
Tried on my Win XP Pro SP2 I removed: -J-Xdock:name=Autopsy and it worked Vic |
Confirming the issue, and solution. Removing the -J-Xdock:name allows Autopsy to run with almost any combination of -J-Xms and -J-Xmx. Prior to removing it, no combination of Xms and Xmx worked. Win7 Pro 64-bit SP1, Java 7u45 |
We're trying to debug why the Xdock:name option removal works (in theory its a mac os x specific option). We've noticed it makes a difference on virtual machines with about 4GB RAM, but not on machines with say 8GB RAM in our environment. Win7 64bit for both of these setups. How much RAM is available in your machines? |
4gb -------- Original message -------- We're trying to debug why the Xdock:name option removal works (in theory its a mac os x specific option). We've noticed it makes a difference on virtual machines with about 4GB RAM, but not on machines with say 8GB RAM in our environment. Win7 64bit for both of these setups. How much RAM is available in your machines? — |
8GB |
16GB Win 7 64 |
NOTE: This was "fixed again" in #3401. Somehow the previous fix never made it back to the develop branch since it was done as a last minute fix during a release. |
Go to C:\Program Files\Autopsy-3.0.8\etc
Edit autopsy.conf (May want to set user permissions to write temporarily while troubleshooting)
Remove -Xdock:name=Autopsy
Save file
Close.
You do not need to modify memory settings on 64 bit autopsy.
The text was updated successfully, but these errors were encountered: