[Oxyd] [0.18.28] Stuck on waiting to save map

Cooldude2606 · Post by **Cooldude2606** » Fri May 29, 2020 7:35 pm

When trying to connect to some multiplayer games it will get stuck on the waiting for server to save map screen. This happans on multiple servers and is more frequent on servers with small maps. I also know, through hosting the deadicated server, that multiple people will experience this while connecting to our server. Our server has non blocking saving enabled if this has any effect. Below are the server logs and client logs when I have the issue. The logs include me pressing esc to cancel the connection as it will just hang with no further log activity. From what I can make of the logs the client never receives mapReadyForDownload and then everything just hangs. The invalid packet states are common to both successful joins and failed joins, and downloading the map never has any issues once it starts.

Server Logs Fail

Client Logs Fail

Code: Select all

 647.474 Joining game IP ADDR:({5.196.93.138:34204})
 647.474 Info UDPSocket.cpp:33: Opening socket
 647.475 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(Ready) to(Connecting)
 647.884 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.884 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.884 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.884 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.884 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.902 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.902 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.902 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.902 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.918 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.951 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 647.983 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 648.018 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 648.050 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
 648.385 Info ClientSynchronizer.cpp:35: Initialized Synchronizer local peer(1) latency(32).
 648.385 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(Connecting) to(ConnectedWaitingForMap)
 648.386 Info ClientRouter.cpp:221: ConnectionAccepted
 648.386 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ConnectionAcceptOrDeny) received from IP ADDR:({5.196.93.138:34204}): invalid state (Connected) for packet type
 648.951 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ConnectionAcceptOrDeny) received from IP ADDR:({5.196.93.138:34204}): invalid state (Connected) for packet type
 649.417 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ConnectionAcceptOrDeny) received from IP ADDR:({5.196.93.138:34204}): invalid state (Connected) for packet type
 721.019 Info ClientMultiplayerManager.cpp:144: Disconnecting multiplayer connection. Reason: Quit.
 721.019 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(ConnectedWaitingForMap) to(DisconnectScheduled)
 721.035 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(DisconnectScheduled) to(WaitingForDisconnectConfirmation)
 721.135 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(WaitingForDisconnectConfirmation) to(Disconnected)
 721.135 Info ClientMultiplayerManager.cpp:891: Disconnect notification for peer (62)
 721.138 Info UDPSocket.cpp:218: Closing socket
 721.138 Info UDPSocket.cpp:248: Socket closed

Server Logs Success

Client Logs Success

Code: Select all

2080.901 Joining game IP ADDR:({5.196.93.138:34204})
2080.901 Info UDPSocket.cpp:33: Opening socket
2080.902 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(Ready) to(Connecting)
2081.285 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.285 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.285 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.285 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.285 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.301 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.301 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.301 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.301 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.316 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.351 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.385 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.418 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.450 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.485 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({5.196.93.138:34204}): invalid state (WaitingForAccept) for packet type
2081.502 Info ClientSynchronizer.cpp:35: Initialized Synchronizer local peer(1) latency(32).
2081.502 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(Connecting) to(ConnectedWaitingForMap)
2081.502 Info ClientRouter.cpp:221: ConnectionAccepted
2082.068 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ConnectionAcceptOrDeny) received from IP ADDR:({5.196.93.138:34204}): invalid state (Connected) for packet type
2082.468 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ConnectionAcceptOrDeny) received from IP ADDR:({5.196.93.138:34204}): invalid state (Connected) for packet type
2082.485 Info ClientMultiplayerManager.cpp:750: Received mapReadyForDownload
2082.485 Downloading file C:\Users\User\AppData\Roaming\Factorio\temp\mp-download.zip (2593302 B, 5156 blocks)
2082.487 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(ConnectedWaitingForMap) to(ConnectedDownloadingMap)
2082.833 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ConnectionAcceptOrDeny) received from IP ADDR:({5.196.93.138:34204}): invalid state (Connected) for packet type
2083.752 Finished download (1 s, 2.5 MB, 2.0 MB/s)
2083.778 Info ClientMultiplayerManager.cpp:730: updateTick(4294967295) map download finished creating scenario
2083.778 Info ClientMultiplayerManager.cpp:581: UpdateTick(4294967295) changing state from(ConnectedDownloadingMap) to(ConnectedLoadingMap)

Cooldude2606 · Post by **Cooldude2606** » Fri May 29, 2020 9:33 pm

To clarify, I have reported this issue before and have had it classed as not a bug. However, this has continually occured since my last report, and people playing on our servers have been reporting this issue to me. I am therefore opening another report as I believe that there is an underlying issue which has not been resolved.

I can also capture a tcpdump/wireshark capture for both the client and server if it would help with debugging.

Here is my previous report from 0.17.44 and a similar report from 0.15.6.

Post by **Rseding91** » Sat May 30, 2020 5:56 pm

I've seen this multiple times before but nobody knows how to reproduce it reliably.

If you can reproduce it (even not reliably) a full process dump of the client and server (assuming it's running windows?) will let me debug it and figure out what's happening.

Cooldude2606 · Post by **Cooldude2606** » Sat May 30, 2020 10:31 pm

The server is running linux headless, will this still be of use? Details for the server and client are below.
Also, when you say process dump, do you mean a net capture or some kind of memory dump?

Server Details

Client Details

Code: Select all

   0.001 2020-05-30 23:23:42; Factorio 0.18.28 (build 52459, win64, steam)
   0.001 Operating system: Windows 10 (version 1909) 
   0.001 Program arguments: "C:\Program Files (x86)\Steam\steamapps\common\Factorio\bin\x64\Factorio.exe" 
   0.001 Read data path: C:/Program Files (x86)/Steam/steamapps/common/Factorio/data
   0.001 Write data path: C:/Users/User/AppData/Roaming/Factorio [77615/446324MB]
   0.001 Binaries path: C:/Program Files (x86)/Steam/steamapps/common/Factorio/bin
   0.026 System info: [CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz, 8 cores, RAM: 7134/16342 MB, page: 12287/18310 MB, virtual: 4326/134217727 MB, extended virtual: 0 MB]
   0.026 Display options: [FullScreen: 1] [VSync: 1] [UIScale: automatic (100.0%)] [Native DPI: 1] [Screen: 255] [Special: lmw] [Lang: en]
   0.037 Available displays: 2
   0.037  [0]: \\.\DISPLAY1 - NVIDIA GeForce GTX 1070 Ti {0x05, [0,0], 1920x1080, 32bit, 60Hz}
   0.039  [1]: \\.\DISPLAY2 - NVIDIA GeForce GTX 1070 Ti {0x01, [-1920,0], 1920x1080, 32bit, 60Hz}
   0.116 [Direct3D11] Display: 0, Output: 0, DisplayAdapter: 0, RenderingAdapter: 0; d3dcompiler_47.dll
   0.316 Initialised Direct3D[0]: NVIDIA GeForce GTX 1070 Ti; id: 10de-1b82; driver: nvldumdx.dll 26.21.14.4187
   0.316   D3D Feature Level: 11.1, DXGI 1.5+, SwapChain: 3,flip-discard,-,-,-,none
   0.316   [Local Video Memory] Budget: 6867MB, CurrentUsage: 4MB, Reservation: 0/3635MB
   0.316   [Non-Local Vid.Mem.] Budget: 7354MB, CurrentUsage: 0MB, Reservation: 0/3881MB
   0.316   Tiled resources: Tier 2
   0.316   Unified Memory Architecture: No
   0.316   BGR 565 Supported: Yes
   0.316   MaximumFrameLatency: 3, GPUThreadPriority: 0
   0.316 Graphics settings preset: very-high
   0.316   Dedicated video memory size 8079 MB
   0.389 Desktop composition is active.
   0.389 Graphics options: [Graphics quality: high] [Video memory usage: all] [Light scale: 100%] [DXT: high-quality] [Color: 32bit]
   0.389                   [Max threads (load/render): 32/8] [Max texture size: 0] [Tex.Stream.: 0] [Rotation quality: normal] [Other: STDC] [B:0,C:0,S:100]
   0.423 DSound: Starting _dsound_update thread
   0.423 DSound: Enter _dsound_update; tid=12672
   0.701 Info ModManager.cpp:253: Found duplicate mod angelsaddons-warehouses, using higher version (0.5.0 > 0.4.1).
   0.730 Info ModManager.cpp:253: Found duplicate mod angelsbioprocessing, using higher version (0.7.6 > 0.6.2).
   0.790 Info ModManager.cpp:253: Found duplicate mod angelspetrochem, using higher version (0.9.6 > 0.8.6).
   0.830 Info ModManager.cpp:253: Found duplicate mod angelsrefining, using higher version (0.11.8 > 0.10.14).
   0.861 Info ModManager.cpp:253: Found duplicate mod angelssmelting, using higher version (0.6.4 > 0.5.7).
   0.904 Info ModManager.cpp:253: Found duplicate mod AutoDeconstruct, using higher version (0.1.17 > 0.1.12).
   0.952 Info ModManager.cpp:253: Found duplicate mod Bio_Industries, using higher version (2.6.17 > 0.17.19).
   0.973 Info ModManager.cpp:253: Found duplicate mod bobassembly, using higher version (0.18.4 > 0.17.7).
   0.988 Info ModManager.cpp:253: Found duplicate mod bobelectronics, using higher version (0.18.1 > 0.17.7).
   1.002 Info ModManager.cpp:253: Found duplicate mod bobenemies, using higher version (0.18.3 > 0.17.7).
   1.020 Info ModManager.cpp:253: Found duplicate mod bobequipment, using higher version (0.18.1 > 0.17.2).
   1.046 Info ModManager.cpp:253: Found duplicate mod bobinserters, using higher version (0.18.1 > 0.17.10).
   1.063 Info ModManager.cpp:253: Found duplicate mod boblibrary, using higher version (0.18.3 > 0.17.5).
   1.121 Info ModManager.cpp:253: Found duplicate mod boblogistics, using higher version (0.18.7 > 0.17.17).
   1.150 Info ModManager.cpp:253: Found duplicate mod bobmining, using higher version (0.18.1 > 0.17.6).
   1.167 Info ModManager.cpp:253: Found duplicate mod bobmodules, using higher version (0.18.2 > 0.17.4).
   1.203 Info ModManager.cpp:253: Found duplicate mod bobplates, using higher version (0.18.5 > 0.17.13).
   1.230 Info ModManager.cpp:253: Found duplicate mod bobpower, using higher version (0.18.4 > 0.17.10).
   1.247 Info ModManager.cpp:253: Found duplicate mod bobrevamp, using higher version (0.18.1 > 0.17.8).
   1.272 Info ModManager.cpp:253: Found duplicate mod bobtech, using higher version (0.18.3 > 0.17.6).
   1.308 Info ModManager.cpp:253: Found duplicate mod bobwarfare, using higher version (0.18.3 > 0.17.11).
   1.474 Info ModManager.cpp:253: Found duplicate mod even-distribution, using higher version (0.3.17 > 0.3.13).
   1.564 Info ModManager.cpp:253: Found duplicate mod FNEI, using higher version (0.3.0 > 0.2.7).
   1.905 Info ModManager.cpp:253: Found duplicate mod rso-mod, using higher version (6.0.6 > 5.0.21).
   2.007 Info ModManager.cpp:253: Found duplicate mod SpaceMod, using higher version (0.5.0 > 0.4.4).
   2.022 Info ModManager.cpp:253: Found duplicate mod Squeak Through, using higher version (1.8.0 > 1.4.0).
   2.142 Loading mod core 0.0.0 (data.lua)
   2.289 Loading mod base 0.18.28 (data.lua)
   3.261 Loading mod base 0.18.28 (data-updates.lua)
   3.456 Checksum for core: 3316124904
   3.456 Checksum of base: 708703854
   3.715 Prototype list checksum: 1311418360
   3.765 Loading sounds...
   9.837 Info PlayerData.cpp:70: Local player-data.json unavailable
   9.837 Info PlayerData.cpp:73: Cloud player-data.json available, timestamp 1590876962
  10.042 Initial atlas bitmap size is 16384
  10.094 Created atlas bitmap 16384x16372 [none]
  10.099 Created atlas bitmap 16384x12772 [none]
  10.100 Created atlas bitmap 8192x3736 [decal]
  10.102 Created atlas bitmap 16384x5152 [low-object]
  10.103 Created atlas bitmap 8192x3744 [mipmap, linear-minification, linear-magnification, linear-mip-level]
  10.103 Created atlas bitmap 16384x5776 [terrain, mipmap, linear-minification, linear-mip-level]
  10.104 Created atlas bitmap 4096x2848 [terrain-effect-map, mipmap, linear-minification, linear-mip-level]
  10.104 Created atlas bitmap 4096x1600 [smoke, mipmap, linear-minification, linear-magnification]
  10.105 Created atlas bitmap 4096x3088 [mipmap]
  10.106 Created atlas bitmap 4096x2144 [icon, not-compressed, mipmap, linear-minification, linear-magnification, linear-mip-level]
  10.106 Created atlas bitmap 2048x192 [icon-background, not-compressed, mipmap, linear-minification, linear-magnification, linear-mip-level, ]
  10.107 Created atlas bitmap 4096x2652 [alpha-mask]
  10.113 Created atlas bitmap 16384x15388 [shadow, linear-magnification, alpha-mask]
  10.113 Created atlas bitmap 8192x2352 [shadow, mipmap, linear-magnification, alpha-mask]
  10.117 Texture processor created (2048). GPU accelerated compression Supported: yes, Enabled: yes/yes. Test passed. YCoCgDXT PSNR: 35.83, BC3 PSNR: 33.82
  14.228 Parallel Sprite Loader initialized (threads: 7)
  22.602 Sprites loaded
  22.614 Generated mipmaps (4) for atlas [3] of size 16384x5152   
  22.625 Generated mipmaps (3) for atlas [4] of size 8192x3744   
  22.636 Generated mipmaps (3) for atlas [5] of size 16384x5776   
  22.647 Generated mipmaps (3) for atlas [6] of size 4096x2848   
  22.659 Generated mipmaps (3) for atlas [7] of size 4096x1600   
  22.701 Generated mipmaps (3) for atlas [8] of size 4096x3088   
  22.713 Generated mipmaps (5) for atlas [9] of size 4096x2144   
  22.725 Generated mipmaps (3) for atlas [13] of size 8192x2352   
  22.734 Custom mipmaps uploaded.
  22.812 Factorio initialised

Post by **Rseding91** » Sat Aug 29, 2020 7:03 pm

Cooldude2606 wrote: ↑Sat May 30, 2020 10:31 pm The server is running linux headless, will this still be of use?

To me; no. I'm not even sure if there is such a thing on linux.

So, there's nothing I can do about this - maybe one of the linux developers could assist.

Cooldude2606 · Post by **Cooldude2606** » Sun Aug 30, 2020 12:10 am

We have done some testing with our server, as well as getting some feedback from other server hosters, and we believe that the banlist might be the cause of the error.

First we filtered our banlist to only include valid usernames (containing alphanumeric characters and ._-) and limited it to bans which included a reason and where the reason contained only ascii characters (without control characters like \n)

We then ran tests with our banlist (On) and then with an empty banlist (Off) allowing upto 10 seconds for the server to save the map, the results follow:
On - 0/3 Successful; Off - 3/3 Successful; On - 0/3 Successful; Off - 3/3 Successful;
On - 1/3 Successful; Off - 3/3 Successful; On - 0/3 Successful

We then stopped as it seamed to be conclusive that the ban list was the cause of these issues, hope this information is helpful.
If you would like me to send the ban list please ask, I would rather send it via dms to avoid posting it publicly.

Post by **Rseding91** » Sun Aug 30, 2020 3:20 am

Is your banlist some huge-ass multiple MB of text? Because it gets sent to connecting players when joining servers to allow a given peer to know if someone is banned or not when using the /ban/unban commands.

mark9064 · Post by **mark9064** » Sun Aug 30, 2020 8:42 am

LOL, we have ~1000 bans on the banlist in total, at a size of 100KiB. I don't think this size is unreasonable, as a large public server the banlist gets to this size after a few years. If you're wondering why no-one else is complaining, other communities have taken to starting games with empty banlists, and then watching the join log for anyone on the real banlist and banning them as soon as they join. This works around the problem of Factorio sending a large banlist which seems to break things, but feels like a solution for a problem that shouldn't exist.

Since these files are just text, compressing them works nicely, dropping the size by a factor of 4 when using GZIP.

Post by **Rseding91** » Sun Aug 30, 2020 5:35 pm

Ok, 100 KB isn't unreasonable but still annoying that it's synced at all. I didn't like it when it was added but saw no other way to do it better at the time. This might give a starting point for figuring out what's happening with stuck saving.

James_Hackett · Post by **James_Hackett** » Fri Oct 16, 2020 1:11 am

Hi Oxyd, any further development on this issue or is there a post I'm missing?

Post by **Oxyd** » Mon Oct 19, 2020 4:11 pm

Hi, and yes, there is a development: It should be fixed for 1.1.0. Thanks for all the information!

jackazzm · Post by **jackazzm** » Mon Oct 04, 2021 5:06 pm

Hello, This issue is plaguing one of the biggest MP servers on factorio quite a lot so it seems to not be totally fixed as of yet

Post by **Klonan** » Mon Oct 04, 2021 7:10 pm

jackazzm wrote: ↑Mon Oct 04, 2021 5:06 pm Hello, This issue is plaguing one of the biggest MP servers on factorio quite a lot so it seems to not be totally fixed as of yet

Can you provide more details, what part is not fixed yet?
Can you make a new bug report with new steps to reproduce, with logs?

jackazzm · Post by **jackazzm** » Tue Oct 05, 2021 11:41 am

Klonan wrote: ↑Mon Oct 04, 2021 7:10 pm
jackazzm wrote: ↑Mon Oct 04, 2021 5:06 pm Hello, This issue is plaguing one of the biggest MP servers on factorio quite a lot so it seems to not be totally fixed as of yet
Can you provide more details, what part is not fixed yet?
Can you make a new bug report with new steps to reproduce, with logs?

It is exactly as OP states, whole server is stuck while 1 player is waiting for the server to save map to them. It is paused until the player decides to abort the connection process so it is very frustrating to have the whole game paused for an unforseen time.

Post by **Klonan** » Tue Oct 05, 2021 1:14 pm

jackazzm wrote: ↑Tue Oct 05, 2021 11:41 am
It is exactly as OP states, whole server is stuck while 1 player is waiting for the server to save map to them. It is paused until the player decides to abort the connection process so it is very frustrating to have the whole game paused for an unforseen time.

Sure, but between then and now the code has changed, so we would need new server logs to help us pinpoint the problem

distortions864 · Post by **distortions864** » Tue Jan 18, 2022 12:43 am

With auth (public game) on, I have been able to reproduce the bug on 1.1.50.

If changing state from(InGameSavingMap) to(InGame) transition to oldState(ConnectedWaitingForMap) newState(ConnectedDownloadingMap) takes longer than a second or two... its locked. Even on huge maps.

I'm not sure I should post the steps to reproduce, because it happens for me 100% of the time. I also posted on the discord in #programming

Here is the map and settings I was using at the time, when trying to reproduce it.
http://m45sci.xyz/u/fact/locker-repoduce.zip
Server and client were ubuntu 20, connecting to my own server locally (but through the server browser)

distortions864 · Post by **distortions864** » Tue Jan 18, 2022 12:02 pm

--Update: Someone sent me a link to the other post about this, for the moment I have made my servers reboot on lock.

Factorio Forums

[Oxyd] [0.18.28] Stuck on waiting to save map

[Oxyd] [0.18.28] Stuck on waiting to save map

Re: [0.18.28] Stuck on waiting to save map

Re: [0.18.28] Stuck on waiting to save map

Re: [0.18.28] Stuck on waiting to save map

Re: [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map

Re: [Oxyd] [0.18.28] Stuck on waiting to save map