FAF crashed on ACU death (with logs)

[Rikai]

What the title says. I was told to post here and to include the logs.
In the exact moment of my ACU dying, the FAF Client (not the game) crashed with the standard windows error message ("stopped working"). Then (of course) lost connection to the enemy.

forever.log:
https://pastebin.com/FcXLnL7U

game.log
https://pastebin.com/R02uFmJy

Replay ID:
7174520
(I watched the replay, there my client does NOT crash)

I guess the line

Code: Select all

pywintypes.com_error: (-2147352567, 'Ausnahmefehler aufgetreten.', (0, None, None, None, 0, -2147220983), None)

from forever.log does sound suspicious.
---
Nothing like this ever happened to me before.
I will update this post if it happens again.

Update:
Annd it happened again...

I use the following UI Mods:
-Common Mod Tools v1.0
-Notifications v5.2
-Supreme Score Board v2.0
-UI Party v13.0
-V2 FA Sequentially Upgrading Extractors v4.0
-Advanced Strategic Icons Mod

Since the bug does not happen every time I die, I cannot practically reproduce.
But news: It happened twice in a laddergame and once in a lobby-based game.

Another thing I noticed:
The replays of crash-on-death-games do not show up in my Local Archive, only on the Online Vault. Maybe that helps too

[Uveso]

Fromt he game.log:

Code: Select all

info: CNetTCPBuf::Read(): recv() failed: WSAECONNRESET

This means, the network socket was forced to close and issued the WSAECONNRESET error.

Maybe a player left the game while gamestats where sended.

PS: IS THERE ANY NEED FOR CAPS OR DO YOU THINK WE ONLY READ BIG TEXT ???

[Rikai]

Thank you for your insight.
Why the salt? I never used caps, just bolded some text. Calm down.

[Rikai]

Aaaaand it happened again. Ok, well, it does not happen in every game, but often enough.
*updated the starting Post
(I better not include the 2nd replay, since it does not seem to have anything to do with the game itself but rather with the client. Besides I played terribad )

[surtsan]

Just a random idea, maybe it is one of the UI mods or a mix of them ?

if it often happens, can you try hosting a lobby then start it alone (for example victory condition sandbox or with bots) and then ctrl k and see if it crashes? And repeat multiple times until it crashes?
If no crashes, then rip my idea.

But if it crashes, then maybe that's a ui mod which is making it crash, try by disabling all ui mods and repeat the same process. If it crashes then the reason is maybe not the ui mods and rip my idea.

If it stops crashing then one of your ui mod is the culprit, you can find which one it is easily. And please tell the result of this idea on this topic.

[Rikai]

Thank you for your input. I tested 6 times against a bot, with Assasination victory condition. Zero crashes.
I suspect it could be the rating system, that should get a "game lost" report on ACU death. Since botgames are not rated, it cannot crash.
I also just played a ladder game, I lost, and it didn't crash. I cannot reproduce reliably yet >.<

Another detail:
When it does crash, the other player gets reported as connection lost (obviously), and I only see my ACU explosion after I eject him. The game still says I lost, like it should, despite ejecting the enemy.

[Uveso]

The picture shows that the FAForever client is crashed, not the game itself.

This is the error why the FAForever client was crashed:

Code: Select all

2017-12-11 16:32:51,599 INFO     fa.upnp                        UPnP mapping 2003:c4:bf0c:bb00:7051:5e26:b87f:a55e:6112
2017-12-11 16:32:51,769 ERROR    fa.upnp                        Exception in UPnP createPortMapping.
Traceback (most recent call last):
  File "src\fa\upnp.py", line 37, in createPortMapping
  File "<COMObject <unknown>>", line 4, in Add
pywintypes.com_error: (-2147352567, 'Ausnahmefehler aufgetreten.', (0, None, None, None, 0, -2147220983), None)

Maybe it could help to simply reset/rstart the router and be sure you have UPnP enabled inside your router.
(Also check if you have already forwarded any needed Port, so maybe the UPnP PortMapping can't use the desired port)

[EDIT]:
The WSAECONNRESET error inside the game was triggered because the FAForever client crashed, and windwos closed the Port.

[Rikai]

It seems like I had indeed trouble connecting to FAF. I opened my port 6112 UDP and since then never experienced this kind of thing again. Seems like your guess at the router was correct. I will play much for some time. If it ever happens again, I will post. The problem seems fixed now.

[Uveso]

Thanks for your reply!