Trond Trosterud wrote: > > My Mac has, as I said, 4 GB RAM, so I thought I might set XMLEditor to > half of it. I am also working with collegues using Windows, so at some > point I will look into their situation also. But I take it my machine is > newer and faster than their, and do not have too big hopes if I cannot > handle the file either. I will have a look at their processor types > etc., but if I understand you correctly, no actual harm is done by > setting the memory limit too high. I anslo understand that Windows users > have a 32-bit OS (Barton's comment), so setting memory to 1.5 GB would > be the appropriate choice (but I'll see what you make out of my file.) > > I really like the XMLEditor, and dictionary work is an obvious way of > using it, so I really hope to find some way of coping with this. >
--> As you can see it in the attached screenshot, it was not a memory problem. In fact, it was a (very uncommon) stack size problem. After changing -Xss1m to -Xss4m, I was able to open your ~3Mb smenob.xml file without any problem. I've changed -Xss1m to -Xss4m in all XXE launchers. Therefore, starting from next release, XXE v3.7, this kind of stack problem should be even rarer than it is today. It took 3 minutes to open smenob.xml on my 3-4 years old, P4 2.2GHz, 2Gb RAM, Linux box. After that, editing smenob.xml was just slightly sluggish (i.e. not great, but usable). --> The workaround for this problem is to increase the stack size of the threads created by Java[tm]. How to do this is described here: http://www.xmlmind.com/xmleditor/faq.html#outofmemory. Just make sure to specify -Xss4m in addition to specifying something like -Xmx1024m (not really needed though). -------------- next part -------------- A non-text attachment was scrubbed... Name: smenob.png Type: image/png Size: 78048 bytes Desc: not available Url : http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20071031/ccc6da60/attachment.png
