Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] Protege 3.4.8 memory/heap size?

Timothy Redmond tredmond at
Tue Aug 21 10:22:37 PDT 2012

If you are working on a windows machine you may be hitting up against an 
install-anywhere bug.  They haven't yet moved to 64 bits so when running 
Protege through install-anywhere you are constrained by the 32-bit 
constraint.  I don't remember the number but that constraint might be 2G 
(the extra addressing bit at the top is lost for some reason?).

If this is the problem then the solution is to use the run.bat file.  If 
you edit this file you can change the heap size by adding a "-Xmx5G" 
parameter like so:

     java -server -Xmx5G -Dlog4j.configuration=file:log4j.xml -DentityExpansionLimit=100000000 -Dfile.encoding=utf-8 -Dorg.protege.plugin.dir=plugins -classpath bin/felix.jar;bin/ProtegeLauncher.jar org.protege.osgi.framework.Launcher


On 8/20/12 10:13 AM, Semir Sarajlic wrote:
> How do I increase the memory available for JVM in Protege 3.4.8.  I 
> have installed the latest JVm (1.7.0_05-b06), which is 64 bit, and in 
> the Java control panel, indicated max memory of 5 GB (I have 8gb of 
> RAM installed).  Also, in Protege, I have changed the max heap size in 
> the lax file to 3.9 gb (If I specify 4GB or more, then Protege does 
> not start up).  However, everytime protege is starting up, it 
> indicates that it has 1849 MB available for JVM (not 3900MB as I 
> indicated in the lax file), and I get out of memory error when I 
> exceed that limit.
> Is there another setting that I am not aware of that could be changed 
> so that I could utilize more than 1849 MB of memory?
> Thanks for the assistance,
> Semir
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at
> Instructions for unsubscribing:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the protege-discussion mailing list