Hi, I am new to this forum. I appreciate any help.

I am running Fedora Core 3 inside Microsoft Virtual PC. I just noticed that Java eats up too much memory.

1. I have Borland C++BuilderX installed. When CBX starts up, System Monitor shows that Java eats up more than 400mb memory! I have also post this to Borland newsgroup, and I think it's solely Borland's matter so I post it here again.

2. If I view a Java applet inside Firefox 1.0, then java_vm eats up more than 200mb memory.

I want to know:

1. If this is normal for Java to eat up so much memory?

2. Is there workaround if it is a problem?

Thanks.

 

 

No, it's not a recognized problem.

How much memory is required to run a simple java program from the command line, or an applet, without any of the other stuff?

In Windows XP Pro + IE, on 1.5_01, I can run the clock applet from the Java JDK demo folder in about 30 mb.

 

 

Doing java -jar welcome.jar shows me that java takes about 214mb memory. Note this is on Fedora Core 3; on Windows java only taks less than 15mb on Windows 2000.

 

 

well, how do you get that values - They sound a bit boguos.

 

 

If I open an applet in firefox I don't see a seperate java_vm process in task manager.

If I use applet viewer to open the BarChart demo I see a peak usage of 14,300K
I am using JDK 1.4.2_05 on Windows 2000.

Generally if the Java is using alot of memory (and you haven't changed the memory parameters) it is because it has loaded alot of libraries. Still it would have to load alot of libraries to reach 200 MB.

 

 

Try running one of the programs mentioned to see how much memory it uses then.

 

 

Thanks for everyong replying.

But please not I am having this memory hog problem on [b]Fedora Core 3[b], which is a Linux variant.

If you have a variant of Linux, can you confirm that the JVM on FC3 is eating up too much memory (more than 400mb)?

 

 

I think I had found a partial answer to my own question.

I can set this option in cbuilder.config to reduce memory footprint:

vmparam -Xmx256m

It reduces about 100mb memory footprint of JVM if I set vmparam -Xmx64m.

So, JVM is out the memory hog problem.

 

 

jvm eats up all memory, growing continusly till it reaches
-Xmx, then starts to take up SWAP without releasing the
SWAP at all, until we manually kill the java application.

There was no load on the java application. this is during off peak
hours, during peak hours java application server has to be restarted
every 1 hour to release SWAP to O/S RHES 3 with Sun 1.4.2_06b

What is stored in SWAP???
Help us