[Rseding91] [2.0.11] Crash placing blueprint over dead stompers body on water (WireRendering::canDrawWiresFromEntity)

[Lappro]

When I tried placing some ctrl-c blueprint of laser turrents and substation to expand defenses on Gleba (using remote view), the game crashed.
The crash occurred directly when clicking to apply the blueprint.
I suspect it might have something to do with it slightly overlapping a dead stomper's body with some water that also needed landfilling for the blueprint.

I'm playing on a dedicated server, which didn't crash. And upon returning to the server the things were built already.
I checked the server logs but there was no saving happening there. (non-blocking saving is enabled there)

Server log snippet around the crash:

Code: Select all

factorio-1  | 148890.232 Info AppManager.cpp:290: Saving to _autosave437 (non-blocking).
factorio-1  | 148890.302 Info AsyncScenarioSaver.cpp:162: Saving process PID: 21750
factorio-1  | 148892.549 Info ChildProcessAgent.cpp:61: Child 21750 exited with return value 0
factorio-1  | 148892.549 Info AppManager.cpp:291: Saving finished
factorio-1  | 149118.465 Info ServerMultiplayerManager.cpp:1083: Disconnect notification for peer (15)
factorio-1  | 149118.465 Info ServerSynchronizer.cpp:613: nextHeartbeatSequenceNumber(8946167) removing peer(15).
factorio-1  | 149490.249 Info AppManager.cpp:290: Saving to _autosave438 (non-blocking).

I was building this part of the north-western defenses on Gleba:

10-26-2024, 13-06-23.png (1.21 MiB) Viewed 758 times

After restarting and reconnecting I did still have the blueprint in my hand.

You can find the save file here, due to size: https://nc.lappro.net/s/FTMq2FRyeEzjaJZ
It is the newest autosave from the server before the crash.

[Lappro]

Same crash happened again, screenshot of the frozen crash screen:

10-26-2024, 14-58-57.png (13.41 MiB) Viewed 736 times

Fresh set of log and dump attached as well.

Most recent autosave put in the Nextcloud link again, but in subfolder "2nd time"

[Lappro]

Happened again, this time on the latest version.

10-26-2024, 21-14-12.png (11.97 MiB) Viewed 699 times

Uploaded to nextcloud again.

This time it also happened to someone else on my server.

[Rseding91]

Thanks for the report. This is now fixed for the next release.

[Lappro]

Thanks!