[0.14.8] [Linux] Crash while playing

[luc]

This is probably going to end up in the "could not reproduce" folder, but thought I'd post it anyway in case you can make sense of it, or if more people have this issue.

I was playing with a few other players (someone else hosted). I think the last thing I did was hit "r" to rotate a red belt into place, or perhaps I hit one of the number keys to select the red belt. I might have been walking around too. Out of nowhere the game crashed, with this log:

Code: Select all

5240.025 Info ClientMultiplayerManager.cpp:763: Disconnect notification for peer (12)
5242.094 Info ClientSynchronizer.cpp:253: Changing local latency from 18 to 16 (nextTickToSend: 3042011, ticksClientWillJumpOver: 0 {})
5242.501 Verbose Scenario.cpp:548: Saving game as /home/$user/Downloads/factorio-0.14.8/saves/_autosave2
5244.144 Verbose Scenario.cpp:642: Time to save game: 1.64288
5249.347 Info ClientSynchronizer.cpp:253: Changing local latency from 16 to 14 (nextTickToSend: 3042312, ticksClientWillJumpOver: 0 {})
5254.350 Info ClientSynchronizer.cpp:253: Changing local latency from 14 to 11 (nextTickToSend: 3042610, ticksClientWillJumpOver: 0 {})
5259.361 Info ClientSynchronizer.cpp:253: Changing local latency from 11 to 18 (nextTickToSend: 3042907, ticksClientWillJumpOver: 0 {})
5269.361 Info ClientSynchronizer.cpp:253: Changing local latency from 18 to 16 (nextTickToSend: 3043510, ticksClientWillJumpOver: 0 {})
5274.463 Info ClientSynchronizer.cpp:253: Changing local latency from 16 to 18 (nextTickToSend: 3043815, ticksClientWillJumpOver: 0 {})
5279.381 Info ClientSynchronizer.cpp:253: Changing local latency from 18 to 23 (nextTickToSend: 3044112, ticksClientWillJumpOver: 0 {})
5289.397 Info ClientSynchronizer.cpp:253: Changing local latency from 23 to 19 (nextTickToSend: 3044715, ticksClientWillJumpOver: 0 {})
5294.391 Info ClientSynchronizer.cpp:253: Changing local latency from 19 to 18 (nextTickToSend: 3045012, ticksClientWillJumpOver: 0 {})
5299.394 Info ClientSynchronizer.cpp:253: Changing local latency from 18 to 17 (nextTickToSend: 3045311, ticksClientWillJumpOver: 0 {})
5304.383 Info ClientSynchronizer.cpp:253: Changing local latency from 17 to 16 (nextTickToSend: 3045610, ticksClientWillJumpOver: 0 {})
5314.386 Info ClientSynchronizer.cpp:253: Changing local latency from 16 to 13 (nextTickToSend: 3046213, ticksClientWillJumpOver: 0 {})
5319.381 Info ClientSynchronizer.cpp:253: Changing local latency from 13 to 15 (nextTickToSend: 3046508, ticksClientWillJumpOver: 0 {})
5329.394 Info ClientSynchronizer.cpp:253: Changing local latency from 15 to 14 (nextTickToSend: 3047111, ticksClientWillJumpOver: 0 {})
5339.383 Info ClientSynchronizer.cpp:253: Changing local latency from 14 to 13 (nextTickToSend: 3047710, ticksClientWillJumpOver: 0 {})
5344.386 Info ClientSynchronizer.cpp:253: Changing local latency from 13 to 14 (nextTickToSend: 3048008, ticksClientWillJumpOver: 0 {})
5349.389 Info ClientSynchronizer.cpp:253: Changing local latency from 14 to 15 (nextTickToSend: 3048309, ticksClientWillJumpOver: 0 {})
5359.395 Info ClientSynchronizer.cpp:253: Changing local latency from 15 to 13 (nextTickToSend: 3048912, ticksClientWillJumpOver: 0 {})
5369.385 Info ClientSynchronizer.cpp:253: Changing local latency from 13 to 22 (nextTickToSend: 3049508, ticksClientWillJumpOver: 0 {})
5379.390 Info ClientSynchronizer.cpp:253: Changing local latency from 22 to 20 (nextTickToSend: 3050113, ticksClientWillJumpOver: 0 {})
5384.393 Info ClientSynchronizer.cpp:253: Changing local latency from 20 to 19 (nextTickToSend: 3050412, ticksClientWillJumpOver: 0 {})
5389.379 Info ClientSynchronizer.cpp:253: Changing local latency from 19 to 17 (nextTickToSend: 3050711, ticksClientWillJumpOver: 0 {})
5399.385 Info ClientSynchronizer.cpp:253: Changing local latency from 17 to 20 (nextTickToSend: 3051310, ticksClientWillJumpOver: 0 {})
5409.391 Info ClientSynchronizer.cpp:253: Changing local latency from 20 to 18 (nextTickToSend: 3051912, ticksClientWillJumpOver: 0 {})
5419.380 Info ClientSynchronizer.cpp:253: Changing local latency from 18 to 16 (nextTickToSend: 3052510, ticksClientWillJumpOver: 0 {})
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Resource id in failed request:  0x22231ec
  Serial number of failed request:  33
  Current serial number in output stream:  35
5432.841 Error CrashHandler.cpp:230: Received SIGSEGV

I'm running Debian testing (Stretch, currently) with Cinnamon as desktop environment.

Let me know if you need any other info or if I could run some test!

[Loewchen]

Please post the complete log.

[luc]

I've posted it as attachment since "Your message contains 97082 characters. The maximum number of allowed characters is 60000."

Not sure where to find that symbolized stacktrace it mentions.

[Klonan]

Thanks for the report,

Have you been able to find anyway to reproduce the issue?
Have you have any other crashes since this one?

[luc]

After this I reconnected to the same server without problems. Spawned right back where I was and was able to complete what I was doing. Played for another 2-3 hours, no crash.

I'll let you know if this occurs again of course, but otherwise I'm afraid I have no steps to reproduce. Like I said:

This is probably going to end up in the "could not reproduce" folder, but thought I'd post it anyway in case you can make sense of it, or if more people have this issue.

[luc]

Same again tonight, while playing multiplayer. I don't want to attach the full log because it contains stuff like auth tokens, IP addresses and local paths. If you need this info, I can send it privately, but not on a public forum.

Last part of the log:

Code: Select all

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Resource id in failed request:  0x2eee0cf
  Serial number of failed request:  20
  Current serial number in output stream:  32
32384.155 Error CrashHandler.cpp:230: Received SIGSEGV
32384.155 Error CrashHandler.cpp:230: Received SIGSEGV
32384.155 Error CrashHandler.cpp:230: Received SIGSEGV
32384.155 Error CrashHandler.cpp:230: Received SIGSEGV
32384.155 Error CrashHandler.cpp:230: Received SIGSEGV
32384.155 Error CrashHandler.cpp:230: Received SIGSEGV

Before that, no messages for 150 seconds. The last one "refusing connection from IP because of player limit." and before that more regular messages related to saving/joins/leaves/heartbeats.

I am running the latest version and my setup is still the same as last time (Debian Stretch and stuff). I hosted the multiplayer game on my laptop. Reading back, last time someone else hosted. Once again it seemed to come out of nowhere.

[Rseding91]

This looks like a Linux driver issue as I can google search the error and get several other pieces of software having the same error and crash.

Some of the results said they did complete driver uninstalls and reinstalls and it fixed the problem for them but it doesn't appear to be anything related to Factorio just that it happens while Factorio is running.

[luc]

... and it just so happens that no other application ever has this issue.

[Rseding91]

... and it just so happens that no other application ever has this issue.

Sorry, there's no way we can reproduce it and you're the only person that has ever reported having this particular issue. Unless you can tell me it's not Linux (reproduce it on Windows/Mac) I still believe it's just a driver problem on your machine or some piece of software you've got running.

[luc]

I can understand others don't have this issue, but it's definitely a combination of something with Factorio since other applications don't have the issue. So I'm fine with you writing it off as wontfix until more people report it, but don't pretend it's a driver thing when my devices and other software work fine.