#4282 Princess-precognition NPE

[Pheonix Rising]

This could be related to the other bug I reported or something different. Basic bug follows:

Exception in thread "Princess-precognition (Independent (Reinforcements))" java.lang.NullPointerException
at megamek.common.Game.getEntities(Game.java:1511)
at megamek.common.Game.getEntities(Game.java:1494)
at megamek.common.MoveStep.isMovementPossible(MoveStep.java:2932)
at megamek.common.pathfinder.MovePathFinder$MovePathLegalityFilter.shouldStay(MovePathFinder.java:181)
at megamek.common.pathfinder.MovePathFinder$MovePathLegalityFilter.shouldStay(MovePathFinder.java:149)
at megamek.common.pathfinder.AbstractPathFinder$Filter.doFilter(AbstractPathFinder.java:113)
at megamek.common.pathfinder.AbstractPathFinder.run(AbstractPathFinder.java:296)
at megamek.common.pathfinder.AbstractPathFinder.run(AbstractPathFinder.java:325)
at megamek.client.bot.princess.PathEnumerator.recalculateMovesFor(PathEnumerator.java:219)
at megamek.client.bot.princess.Precognition.run(Precognition.java:196)
at java.lang.Thread.run(Unknown Source)

Best I can tell this happened when a vee was set to move. Attaching logs and save.

[Pheonix Rising]

log and save at time of crash

[Nicholas Walczak]

This is the same stack trace as in [#4261], so I'm going to mark it as a duplicate. My guess is that this is a concurrency issue, and there are several tickets currently open related to Princess and concurrency. Deric is working on it.