In my module ‘Barbarossa Army Group South 1941’ a new exception has emerged since Vassal was raised to 3.2.2
When a pop-up chart is opened it will generate an unhandled exception and cause the chart to fail if the chart is re-sized by selecting any edge and pulling it. It is only on charts this has happened, not on other pop-up windows.
The module was designed under the 3.1.20 version, and had no problems on that version.
The problem is repeatable, although not always on first re-size.
Thus spake Darkebear:
In my module ‘Barbarossa Army Group South 1941’ a new exception has
emerged since Vassal was raised to 3.2.2
When a pop-up chart is opened it will generate an unhandled exception
and cause the chart to fail if the chart is re-sized by selecting any
edge and pulling it. It is only on charts this has happened, not on
other pop-up windows.
The module was designed under the 3.1.20 version, and had no problems on
that version.
Have you reported the exception using the bug dialog?
–
J.
All I’ve done so far is upload the vassal-generated error file and followed the instructions when the Bug popped-up. First time I’ve reported one. I did try the bug dialogue, but I could not seem to get it to post anything.
I tried to use the Bugzilla page, but I’m not having any success in using it.
G.
Thus spake Darkebear:
All I’ve done so far is upload the vassal-generated error file and
followed the instructions when the Bug popped-up. First time I’ve
reported one. I did try the bug dialogue, but I could not seem to get it
to post anything.
Is this the bug you reported via the bug dialog?
vassalengine.org/tracker/sho … gi?id=9692
I think it must be.
This is a Java bug, not a bug in VASSAL. Sadly, Oracle doesn’t care
that there’s a race condition in their display code, so I don’t have
any hope that it will ever be fixed:
bugs.sun.com/view_bug.do?bug_id=6933331
The only workaround we can provide is a preference for turning off
DirectX D3D, since the problem tends to occur in that graphics pipeline
but not the others. (Check your Preferences for this setting.) There’s
nothing else we can do about it, since the stack trace for this bug
doesn’t go through any of our code.
Problems like these are reasons why we’re not using Java for VASSAL 4.
–
J.
Thanks for the analysis and your time.
I also come from a coding background (C++) so know the useful but fickle nature of Java.
If there is not already an option to turn off resizing on any Charting windows, then perhaps it can be added to the next minor 3.2 release?
I’d like to make the next module as rhobust as I can within the Vassal framework available to me, so if I can at least turn-off this feature, then it is a fix I can use.
G.
Thus spake Darkebear:
Thanks for the analysis and your time.
I also come from a coding background (C++) so know the useful but fickle
nature of java.
If there is not already an option to turn off resizing on any Charting
windows, then perhaps it can be added to the next minor 3.2 release?
I’d like to make the next module as rhobust as I can withing the Vassal
framework available to me, so if I can at least turn-off this feature
then it is a fix I can use.
Are you still able to reproduce this problem with VASSAL 3.2.6 and the
current version of Java (which is 7 Update 21 at present)?
–
J.
The problem seemed to disappear on one of the updated Vassal versions. I’ve not experienced it for several months of regular use of the module now - presently still on 3.2.4 release, so not yet tried the later ones.
Over the next few days I’ll update to 3.2.6 and try to cause the fault and report.
G.
OK - tried 3.2.6 and it still seems OK.
Pulled and resized without the exception. Originally it would cause the exception most of the time it was re-sized, so the problem is either resolved, or a lot better!
G.