I’m getting consistent errors with 3.5.4. However, I’ve yet to see any actual bad behavior from it. I just get an ‘eek!’ message.
Letting Vassal send a bug report on it’s own fails (I don’t think I’ve ever seen that work, not just with this).
Steps to reproduce:
open log file
start a new log
start stepping through the original log, recording reactions, etc.
when you hit the end of the original log, the error box comes up
I’ve attached the log file, which took some doing as it doesn’t natively have a regular extension, and the forum software doesn’t allow *.4 attachments, and you can’t just copy and paste because the text is too long for a forum post…
I did not debug the code, but I am pretty sure it occurs when you keep the PgDown pressed to fast forward a log to its end.
Doing that might fill a buffer of unprocessed PgDown after the log is completed.
YOu can see that not occurring if you play the log slowly to the end.
There have been rare occasions when it’s thrown an error over the years, and I’ve hit the ‘report bug’ function… and it generally fails in my memory.
As far as the error reported… SNAPSHOT-b4b7d8d fixes it. I was a little surprised as Claudio’s diagnosis was definitely off, as I step through a log one action at a time, seeing what my opponent is doing, and not racing through it, and it gave the exception/bug with a single keypress.
…Though, just actually checked that case too, and no problems with racing through a log while recording one.
Interesting, this happens to me most if not all of the time and I assumed that the bug reports weren’t getting through. Sometimes I will copy the dump and post an error report and sometimes I don’t.
The report, if it is the same one, is simply the Vassal “eeeek” box updating to inform you that the bug report didn’t get through and please email it in manually (with the dump still available in the window).
Well, the bug I reported on here was fixed in SNAPSHOT-b4b7d8d, so that doesn’t cause an error window any more. Thankfully, I remembered another one I ran across:
Vassal seems to be automatically generating a ‘Player Sides’ component for a module, even if there’s no intention of ever using player sides in a module. Deleting that component and then starting a new game generates an uncaught exception error.