[mkgmap-dev] Splitter output files are nearly empty
From Thorsten Kukuk kukuk at suse.de on Tue May 3 22:25:10 BST 2011
On Tue, May 03, Lambertus wrote: > On 03-05-11 20:01, Marko Mäkelä wrote: > > On Tue, May 03, 2011 at 05:48:55PM +0200, Lambertus wrote: > > I assume that GC means garbage collection. Which JVM are you using? An > > educated guess is that the memory runs out and a "full garbage > > collection" cycle is started as a last resort. > > > Ok, "Garbage Collection" sounds reasonable, but I gave Java 7.5 GB heap > space while it used only a few hundred megabytes. I've got no idea why > it would run out of memory. Do you really have so much free memory available? If you tell Java it should use 7.5GB heap space, it will use that, even if not available, and fail. I run Java with 4GB heap space (machine had more), but since other processes allocated memory, too, it did fail sometimes with similar symptoms. After I reduced the memory to 2.5 GB heap space, it runs fine. -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
- Previous message: [mkgmap-dev] Splitter output files are nearly empty
- Next message: [mkgmap-dev] Splitter output files are nearly empty
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list