Skip to content
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

Closed
staridlabs opened this issue Dec 3, 2013 · 7 comments
Closed

FIX: Autopsy 3.0.8 Java "Cannot create Java Virtual Machine" #379

staridlabs opened this issue Dec 3, 2013 · 7 comments

Comments

@staridlabs
Copy link

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.

@Vic152
Copy link

Vic152 commented Dec 3, 2013

Tried on my Win XP Pro SP2

I removed: -J-Xdock:name=Autopsy

and it worked

Vic

@isokcevic
Copy link

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

@jletourneau-basistech
Copy link
Contributor

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?

@staridlabs
Copy link
Author

4gb

-------- Original message --------
From: jletourneau-basistech [email protected]
Date:01/24/2014 7:55 AM (GMT-06:00)
To: sleuthkit/autopsy [email protected]
Cc: staridlabs [email protected]
Subject: Re: [autopsy] FIX: Autopsy 3.0.8 Java "Cannot create Java Virtual
Machine" (#379)

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?


Reply to this email directly or view it on GitHub.

@isokcevic
Copy link

8GB

@Vic152
Copy link

Vic152 commented Jan 26, 2014

16GB Win 7 64

bcarrier added a commit that referenced this issue Jan 28, 2014
@bcarrier
Copy link
Member

bcarrier commented Feb 1, 2018

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.

@bcarrier bcarrier closed this as completed Feb 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants