[Gvsig_english] POTENTIAL ERROR gvSIG 1.9 (BN 1253) -- Jave Heap Error while editing table

[Benjamin Ducke]

Also note that under Linux you can set the heap space
much larger than under Windows. In my experiments on Win XP,
gvSIG would no longer start up if I set Xmx to > 1500 or so.
Try how far you can go.

Ben

----- Original Message -----
From: "Jorge Piera" <jorge.piera at iver.es>
To: "Users and Developers mailing list" <gvsig_internacional at listserv.gva.es>
Sent: Friday, January 8, 2010 8:45:48 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
Subject: Re: [Gvsig_english] POTENTIAL ERROR gvSIG 1.9 (BN 1253) -- Jave Heap Error while editing table

Hi.

The optimum setting for memory depends on your environment and the 
application that your are running. I would try values from 500MB up to 1GB.

Regards,
Jorge.

Simon Cropper (Botanicus Australia Pty Ltd) wrote:
> Jorge,
>
> My settings are command = #JAVA# 
> -Djava.library.path="#GVSIG_INSTALL_PATH#\lib" -cp #CLASSPATH# -Xmx500M 
> -Xss1024k com.iver.andami.Launcher gvSIG gvSIG/extensiones #ARGS#
>
> What is the optimum setting for memory? I run a Windows XP SP3 2GB of 
> memory.
>
> Cheers Simon
>
> Simon Cropper
> Botanicus Australia Pty Ltd
> PO Box 160, Sunshine, Victoria 3020.
> P: 9311 5822. M: 041 830 3437.
> mailto: scropper at botanicusaustralia.com.au 
> <mailto:scropper at botanicusaustralia.com.au>
> web: www.botanicusaustralia.com.au <http://www.botanicusaustralia.com.au>
>
>
> On 8/01/2010 5:52 PM, Jorge Piera wrote:
>   
>> Hello Simon.
>>
>> Hi.
>>
>> You can run gvSIG using more memory. Just edit the gvSIG.sh (or the
>> gvSIG.ini) file located in the installation directory (folder bin) and
>> find the text "-Xmx500M". 500M is the number of MB that you want to use
>> when you execute the Java Virtual Machine. You can change this number by
>> the number of MB that you want and next time that you run gvSIG, it will
>> use this number of MB./
>> /
>> Regards,
>> Jorge.
>>
>>
>> Simon Cropper (Botanicus Australia Pty Ltd) wrote:
>>    
>>     
>>> Hi,
>>>
>>> I managed to generate a Java Heap error in gvSIG.
>>>
>>> Unfortunately I was unable to capture any error details.
>>>
>>> I can tell you what I was doing and hopefully you can reproduce.
>>>
>>> I was editing a shapefile's attribute table. Specifically I was changing
>>> the values of a field used in complex labeling in individually defined
>>> labeling classes - 10W = 10m high white writing, 5W = 5m high white
>>> writing, etc.
>>>
>>> The shapefile is present 3 times in ToC. The first is site #, second
>>> vegetation type, third quality. The label sizre is based on a field
>>> called [LglGrp]. I was editing this field when I asked myself what the
>>> previous instance of the shapefile looked like. Without really thinking
>>> I clicked on the first instance (Site #) of the shapefile to view the
>>> labels (without saving my changes) and BANG all hell broke loose - I had
>>> numerous Java Heap Errors.
>>>
>>> I exited the program without saving and reentered. The shapefile was
>>> intact but the recent edits were lost (obviously). I have scoured the
>>> system but no error log was found.
>>>
>>> I have tried to repeat my steps but have not been able to triggered the
>>> error again.
>>>
>>> Anyone know what would have triggered such a response? Memory issues?
>>>
>>>      
>>>       
>>    
>>     
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at listserv.gva.es
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>
>
>   


-- 
Jorge Piera Llodrá
Especialista en Servicios OGC
Equipo de desarrollo gvSIG
IVER TI S.A.
C/ Lérida, 20
46009-Valencia (Spain)
Tlf.+34902252540
www.iver.es
www.gvsig.com  

_______________________________________________
Gvsig_internacional mailing list
Gvsig_internacional at listserv.gva.es
http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional



------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.