Dell D531. (I’ve also encountered it on other machines too)
Fresh install of Windows XP 32-bit (Thus, none of the software mentioned here will be 64-bit)
Latest download and install of Eclipse Developer EE (3.6.1)
Run Eclipse: No problems.
Install latest version of Comodo Firewall. (cfw_installer_x86.exe ver. 5.3.174622.1216)
Run Eclipse: No problems.
Modify Eclipse.ini to set -Xmx###m from 512 to anything above 736
Save the file
Start Eclipse.exe:
“Failed to create the Java Virtual Machine”
Start Eclipsec.exe:
“Error occurred during initialization of VM”
“Could not reserve enough space for object heap”
I can disable every single bit of Comodo (Defense+ permanent, Sandbox Disabled, Firewall Disabled) and will still have the above problems. (Though, from my experience, ‘turning off’ anything in Comodo seems to do very little. The rules still seem to apply for many things.)
Uninstall Comodo; run Eclipse.exe: No problems.
Why is Comodo preventing me from creating a large JVM? I’m developing a java application that works with large databases and need several gigs of heap space. How do I resolve this?
Setting it as a “Trusted” application doesn’t seem to work. It doesn’t even seem to accept it, as it won’t set it as trusted without the exe being “signed”.
Is there any way to make Comodo just act like a firewall? I’d rather it didn’t monitor applications and memory footprints.
(I did a search about this but didn’t turn up any real answers. Placed it in this forum as it seems it would be outside “Firewall” part of the program if it’s monitoring applications and memory size.)
It seems linked to this same problem: http://forums.Comodo.com/bug-reports/imagej-java-virtual-machine-launcher-could-not-start-x32-3014276-t18075.0.html
But that forum post is from years ago, regarding Comodo Firewall version 3.0. Has this been a problem since then, or has it simply returned?
This link: https://forums.Comodo.com/empty-t49144.0.html
is from only a month ago, so it would seem to support that this bug has just again cropped up.
I appreciate any and all help with this issue.
Edited: Update: I was running 5.0.16 on another machine with no issues. Version 5.3.174622.1216 has this issue. I’m starting to wonder if this isn’t actually a bug.