Multiplayer scenario crash after adding and removing players

[Benderman8879]

• Game Version: Premium

• Build Number: v.100.18.49472.0 (573760R)

• Platform: Steam

• Operating System: Windows 11 and Linux

Issue:

This is a pretty obscure problem, but it consistently crashes the game for us.

If you add and remove players enough times from a custom scenario, then try to host that scenario, the game crashes immediately when the scenario is loaded.

The dump file that got saved when the game crashed included the following info:
Crash reason: EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x350000003b

Trigger Event:

Once both players are ready in the lobby, the game countdown starts and the game loads into the scenario. As soon as the map is visible, the game crashes.

I came across this issue in a couple of coop campaign scenarios, but it can also be reproduced using a two-player scenario with no units or triggers. The game does not crash when playing the same scenario in singleplayer.

Repro Steps:

1. Create a new scenario
2. Open the Scenario > Player Data panel
3. Change the number of players to 12 and click Apply
4. Change the number of players to 1 and click Apply
5. Change the number of players back to 12 and click Apply
6. Change the number of players back to 1 and click Apply
7. Change the number of players to 2 and click Apply
8. Save the scenario
9. Host a new multiplayer game, selecting the scenario that was just created
10. Invite a second player and click Ready
11. The game crashes as soon as the players load into the level and the bugsplat window is shown

[Benderman8879]

It seems this crash can be worked around by explicitly setting the team for the second player. I assume without setting a team, the game tries to assign them to a team that is outside the available 12 teams that can be chosen normally.

Also worth pointing out that this bug continues to affect a scenario even after closing and reopening the game or saving the scenario as a new file.