Maxing out Java Heap at 799mb

[stuckless]

But are you running standard 32bit Java? Which version? What OS? How much memory? Mainly curious, I've read the max VM size possible is theoretically ~1900MB.

java version "1.6.0_15"
Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
Java HotSpot(TM) Server VM (build 14.1-b02, mixed mode)

OS is 32bit Ubuntu 9.10 with 4gig installed memory but only 3.2gigs visible. Someday if i even need the other .8gig, then I'll enable a pae kernel.

I forget, are you using DVDPro2Sage or did you roll your own DOM parser? I've got a working but not thoroughly tested, and not worked on for a while SAX parser.

I rolled my own mainly because how dvdpro2sage works and how core bmt works are very different. bmt providers are only passed a title, but dvdpro2sage uses the filepath (from what I recall). I'm actually in the process of making some changes to bmt to allow it to pass a filepath to a provider and when that's complete, I'll be able to use dvdpro2sage as a provider.

[stanger89]

Originally Posted by stuckless

java version "1.6.0_15"
Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
Java HotSpot(TM) Server VM (build 14.1-b02, mixed mode)

OS is 32bit Ubuntu 9.10 with 4gig installed memory but only 3.2gigs visible. Someday if i even need the other .8gig, then I'll enable a pae kernel.

Hm, maybe it's something different with the Linux java....

I rolled my own mainly because how dvdpro2sage works and how core bmt works are very different. bmt providers are only passed a title, but dvdpro2sage uses the filepath (from what I recall).

DVDPro2Sage actually just takes the title, only path it needs is the path to the dvd profiler XML.

I'm actually in the process of making some changes to bmt to allow it to pass a filepath to a provider and when that's complete, I'll be able to use dvdpro2sage as a provider.

I doubt it's worth that, I don't think DVD Pro2Sage does anything your solution doesn't, and the code is probably a lot uglier

[koan00]

http://www.unixville.com/%7Emoazam/2004/06/03.html

Accordign to this, JVM limit to under 2GB on 32 bit windows is due to problems with windows. Not the JVM. Hence it differs on Linux. I would suspect a 64bit windows and 64Bit JRE would act differently as well.

[jason22]

Originally Posted by koan00

http://www.unixville.com/%7Emoazam/2004/06/03.html

Accordign to this, JVM limit to under 2GB on 32 bit windows is due to problems with windows. Not the JVM. Hence it differs on Linux. I would suspect a 64bit windows and 64Bit JRE would act differently as well.

Yes, I believe we ran into this same issue at work once, but I couldn't remember the specifics. It was a windows 32 bit specific limitation. It did not apply on other operating systems