Open GoogleCodeExporter opened 9 years ago
Hello,
Thanks for the error report: it was very helpful in finding the root cause.
Unfortunately, it is not something that can be fixed quickly. For the
technically minded: a data structure is accessed from multiple threads but no
synchronization mechanism is in place to prevent corrupting the data structure
by simultaneous operations by different threads (in brief: a threading issue)
The results can be unpredictable.
This particular data structure is used in several parts of the code, that is
why a quick fix is not realistic (only doing this in my spare time) but it is
on my todo list, so eventually I might get to it.
Regards,
Eddy.
Original comment by evil...@gmail.com
on 25 Sep 2014 at 5:19
Thanks for looking into the error. I suggest that even if right now we lack
the means to fix it, we still accept this issue since it was reported correctly
and we understand that it's a defect.
Original comment by DandyD...@gmail.com
on 8 Nov 2014 at 7:27
Here again the error with the ghost rook:
Error occured! We are trying to make Raptor bug free and we need your help!
Please take a moment to report this issue by selecting the menu:
Help -> Report Issue
Error in ThreadService Runnable.
NullPointerException:
java.lang.NullPointerException
at raptor.chess.pgn.PgnUtils.getMove(Unknown Source)
at raptor.chess.ClassicGame.toPgn(Unknown Source)
at raptor.chess.pgn.PgnUtils.appendGameToFile(Unknown Source)
at raptor.swt.chess.controller.PlayingController$2$2$1.run(Unknown Source)
at raptor.service.ThreadService$RunnableExceptionDecorator.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
Original comment by christia...@gmail.com
on 15 Nov 2014 at 10:49
Thanks for the additional info. Like mentioned before, the underlying problem
has been identified, but is not something that can be fixed quickly (meaning:
more time than I can devote to Raptor maintenance for now)
From the information that you provided, I can conclude that the issue depends
on exact timing of several events, some of which that the Raptor user has no
control over (events coming in from the chess server) That means that under
most circumstances, you would not see this error, but I do aggree that when it
happens, it can very annoying.
Original comment by evil...@gmail.com
on 15 Nov 2014 at 2:47
Its annoying, but I am getting useed to it, needs some extra creativity ;-).
Raptor is such I great interface and I am so thankful for the brilliant work
you are providing, so I could wait!
Original comment by christia...@gmail.com
on 15 Nov 2014 at 2:51
Original issue reported on code.google.com by
christia...@gmail.com
on 25 Sep 2014 at 12:56