Over a specific valuet: java.lang.OutOfMemoryError

[elect]

Hi all,

Here the code

vertexData = GLBuffers.newDirectFloatBuffer(triangleNumber*3*3);
      for(int i=0; i<triangleNumber; i++) {
          Triangle tmp = triangleArray.get(i);
          vertexData.put(new float[]{tmp.x1/12000.0f, tmp.y1/12000.0f, tmp.z1/12000.0f, 
                                     tmp.x2/12000.0f, tmp.y2/12000.0f, tmp.z2/12000.0f, 
                                     tmp.x3/12000.0f, tmp.y3/12000.0f, tmp.z3/12000.0f  });

The problem arises when triangleNumber is bigger than about 2 milions

It seems that the default size is around 64 MB (2M = 68MB)

-XX:MaxDirectMemorySize=256M didnt help >.>

I would need, lets say, to allocate up to 10 milions of triangles (then 10 M *3*3) to push them later in the gpu framebuffer, but 5 can be already a nice solution

Any idea?

[quad64bit]

The java.lang.OutOfMemoryError is pretty generic, have you tried just increasing the VM memory allocation?

-Xmx512m -Xms512m

Something like that?

[Tolls]

From the docs for -XX:MaxDirectMemorySize:
This option specifies the maximum total size of java.nio (New I/O package) direct buffer allocations.

Not really what you want...
quad64bit has given you the proper switch (-Xmx).

[elect]

The java.lang.OutOfMemoryError is pretty generic, have you tried just increasing the VM memory allocation?

-Xmx512m -Xms512m

Something like that?

I had a java heap overflow and I solved with the first argument that you mention

Right now my arguments are the following, but unfortunately the second one seems to be superfluous

-Xmx1500m -XX:MaxDirectMemorySize=256M

From the docs for -XX:MaxDirectMemorySize:
This option specifies the maximum total size of java.nio (New I/O package) direct buffer allocations.

Not really what you want...
quad64bit has given you the proper switch (-Xmx).

The crash in the console points at the part of code that I illustrated in the first post. And it happens only when triangleNumber is about bigger than 2M so I guess it should be something related to the buffer allocation..no?

[Tolls]

NIO is the New Input/Output package.
It's entirely related to IO...nothing to do with general memory management, or OOM exceptions.
You are not doing any IO there (or using that package) so that parameter is irrelevant.

[JosAH]

NIO is the New Input/Output package.
It's entirely related to IO...nothing to do with general memory management, or OOM exceptions.

Well, sort of; the NIO package uses the system calls mmap, munmap and compadres (for mapping files to (virtual) memory) and they can take up quite some memory in the process space. I don't know if that memory resides in Java's heap space or not ... (I think it does)

kind regards,

Jos

[Tolls]

Well, sort of; the NIO package uses the system calls mmap, munmap and compadres (for mapping files to (virtual) memory) and they can take up quite some memory in the process space. I don't know if that memory resides in Java's heap space or not ... (I think it does)

kind regards,

Jos

But is the OP using any NIO stuff?
There's nothing in that post to suggest it...and if it is the case then maybe it might have been an idea to point it out?

In any case I'd have thought the memory error would have been different than a base heap one if it were to do with NIO.

[JosAH]

But is the OP using any NIO stuff?
There's nothing in that post to suggest it...and if it is the case then maybe it might have been an idea to point it out?

In any case I'd have thought the memory error would have been different than a base heap one if it were to do with NIO.

All true; I was just thinking in a nuts and bolts kindof way. NIO stuff can take up a lot of memory, but the OP wasn't using any NIO classes, so I'll keep my mouth shut and think my low level things again ;-)

kind regards,

Jos

[Tolls]

Know your place...

[JosAH]

Know your place...

Aye aye 'squire, can I go back to my corner and do my low level nuts and bolts deeds now, please?

kindest regards,

Jos

[quad64bit]

I've also had strange memory errors in the past with large web apps. In that case, adjusting the perm size helped:

-XX:MaxPermSize=256m -XX:PermSize=128m

FYI the second argument isn't required, but I like to set minimums for certain contexts!

[elect]

I've also had strange memory errors in the past with large web apps. In that case, adjusting the perm size helped:

-XX:MaxPermSize=256m -XX:PermSize=128m

FYI the second argument isn't required, but I like to set minimums for certain contexts!

Unfortunately:

Error occurred during initialization of VM
Error: Could not create the Java Virtual Machine.
Could not reserve enough space for object heap
Error: A fatal exception has occurred. Program will exit.
Java Result: 1

[Tolls]

I've also had strange memory errors in the past with large web apps. In that case, adjusting the perm size helped:

-XX:MaxPermSize=256m -XX:PermSize=128m

FYI the second argument isn't required, but I like to set minimums for certain contexts!

That would give a different exception message.

Unfortunately:

In which case you need to give it less memory...you are either exceeding your system or, more likely, the limitation of a Java 32 bit JVM (1.5 G?).

[elect]

That would give a different exception message.



In which case you need to give it less memory...you are either exceeding your system or, more likely, the limitation of a Java 32 bit JVM (1.5 G?).

Solved by switching from xp 32b to 7 64b :)