Thus spake Todd Pytel: > Hi Joel, > > On Mon, 2007-11-12 at 23:48 +0100, Joel Uckelman wrote: > > You might be running out of memory, and having it fail silently. Tunisia > > uses a large map and starts at a zoom level which isn't 1:1, which takes > > more memory still. For now, try increasing the amount of memory which you > > let the JVM use. > > Are you referring to the "max-heap-size" parameter found in the .jnlp > file? If so, mine was set to 1024M by default. I increased it to 2048M > (my total physical memory), but that didn't change anything either. > > Any other suggestions? I have a very cursory understanding of Java > programming - not enough to really debug anything myself, but I could > probably use debugging tools to get some better information with a bit > of guidance. > > --Todd
(I've already sent a version of this to Todd; here's an update for those playing along at home.) Short version: This problem has nothing to do with the Tunisia module, memory settings, or VASSAL. It's a problem with Java, and it only affects Linux users running particular window managers. Long version: If you're using a non-reparenting window manager on Linux---Beryl, Compiz, and Compiz Fusion are all examples of these---then you might find that some windows in VASSAL either lack some of the widgets (buttons, scroll bars, etc.), are unable to display images, or both. This is due to some bad code in the JVM, as discussed here: http://bugs.sun.com/view_bug.do?bug_id=6509038 There's nothing we can do about this on the VASSAL end of things---we're stuck waiting for Sun (or, now people contributing code to the open-source Java 7) to fix this. This probably doesn't affect all that many people---Linux users who are using compositing window managers, mainly---but if you're one of them, now you know why it's happening. Ultimately, the fix will involve upgrading to some version of Java 7. For reference, it's not fixed in 1.7.0.0-0.19.b21, which is what I'm using on my Fedora 8 system. -- J.
