Closed andy5995 closed 6 years ago
Please try the latest git and see if this can be reproduced. I tried a fix for this use case.
This has only happened 2x in the last six months, but I'll definitely report if it happens again.
Can you say if it's possible that having "shared resources" on may have something to do with it? If so, we can play more games with shared resources on to test for it.
Its hard to say exactly what triggers this, but it does 'look' like it may be related to shared teams. Essentially a peer units command has no unit type when we expect it to have one (during a repair). Now in such a case I wont try to continue in this case so the null error should no longer be triggered.
ok. And to be clear, during today's game, "shared teams" was off, "shared resources" was on.
Can we close this?
I'd say more testing is needed because of how rarely it happened; or close for now and reopen if it's reported again.
I say we keep it open to track it if it happens again.
There are 2 forum posts related to this:
3.9.1: unit_updater.cpp::updateRepair Line: 2170] Error [ut == NULL https://forum.megaglest.org/index.php?topic=9490.0
error NULL crash
Today it happened while playing with shared units. So far that may be the only clue as to reproducing it.
Also, it happened immediately after I selected to build a library, (but I hadn't placed it yet). And looking at the screenshot, I see there wasn't enough wood.
See this forum post for more details about today's game.
The game crashes for all players at the same time.
Run from the headless dev server.