-Xmx100m works vs -Xmx300m

Thread view:

Dado - 20 Jan 2006 21:06 GMT

I have an OutOfMemory exception when I try to print 2DGraphics, with the
next options of a java launcher:
java -Xms80m -Xmx100m -XX:PermSize=64m -Xss64m -verbose:gc

I tried:
java -Xms100m -Xmx300m -XX:PermSize=64m -Xss64m -verbose:gc
but now I got OutOfMemory exception even before printing, in a opening
database process.

Machine is Athlon 1500+ with the 512MB RAM.

Reply to this Message

neo - 23 Jan 2006 05:08 GMT

Why You need -Xss to 64m are you using lot of thread locals? If you
have multiple threads, the memory will exhaust on thread creation.

Nirav

Reply to this Message

Dado - 23 Jan 2006 19:16 GMT

"neo" <nirav.thaker@gmail.com> je napisao u poruci interesnoj
grupi:1137992939.492947.276240@f14g2000cwb.googlegroups.com...

> Why You need -Xss to 64m are you using lot of thread locals? If you
> have multiple threads, the memory will exhaust on thread creation.
>
> Nirav

That is one of uncleared facts. In a code, I created only one thread (when I
show print dialog), but in a NetBeans profiler I was surprised with a 12-15
threads. So I don't no, in a practise, what is the optimal setup for that
number of thread, on the average machine (128RAM)..

Reply to this Message

neo - 24 Jan 2006 10:46 GMT

There are several system threads which run as daemon ( finalizer, gc,
hotspot detector etc, which depends on wich jvm you are using). Why
dont you remove (or reduce) -Xss parameter.

Nirav

Reply to this Message

-Xmx100m works vs -Xmx300m

Free Magazines