[0.17.4] [Linux] Stops during loading at "Building prototypes..."

[Svip]

On Fedora 28.

Code: Select all

4.19.12-200.fc28.x86_64 #1 SMP Mon Dec 24 02:18:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

When I start Factorio from Steam, it stops at either 15 or 29% with the description "Building prototypes..." and nothing further happening.

From factorio-current.log:

Code: Select all

   0.000 2019-03-03 13:18:20; Factorio 0.17.4 (build 43174, linux64, steam)
   0.277 Operating system: Linux (Fedora 28)
   0.277 Program arguments: "/home/svip/SteamLibrary/SteamApps/common/Factorio/bin/x64/factorio" 
   0.277 Read data path: /home/svip/SteamLibrary/SteamApps/common/Factorio/data
   0.277 Write data path: /home/svip/.factorio [83792/420446MB]
   0.277 Binaries path: /home/svip/SteamLibrary/SteamApps/common/Factorio/bin
   0.287 System info: [CPU: AMD Ryzen 7 1800X Eight-Core Processor         , 16 cores, RAM: 32155 MB]
   0.287 Environment: DISPLAY=:1.0, WAYLAND_DISPLAY=<unset>
   0.287 Display options: [FullScreen: 1] [VSync: 1] [UIScale: automatic (100.0%)] [MultiSampling: OFF] [Screen: 255] [Lang: en]
   0.390 Available displays: 2
   0.390  [0]: BenQ G2420HDB 22" - {[0,0], 1920x1080, SDL_PIXELFORMAT_RGB888, 60Hz}
   0.390  [1]: BenQ BL2400 22" - {[1920,0], 1920x1080, SDL_PIXELFORMAT_RGB888, 60Hz}
   0.456 Initialised OpenGL:[0] GeForce GTX 970/PCIe/SSE2; driver: 3.3.0 NVIDIA 415.25
   0.456   [Extensions] s3tc:yes; KHR_debug:yes; ARB_clear_texture:yes, ARB_copy_image:yes
   0.456   [Version] 3.3
   0.490 Graphics settings preset: very-high
   0.490   Dedicated video memory size 4096 MB
   0.491 Graphics options: [Graphics quality: high] [Video memory usage: all] [Light scale: 25%] [DXT: high-quality]
   0.491                   [Max load threads: 32] [Max texture size: 0] [Tex.Stream.: 0] [Low quality rotation: 0]
   0.493 errno: 16 -- Device or resource busy

   0.493 Failed to init OSS.

   0.493 No audio driver can be used. (error code: 1)

   0.493 Warning GlobalContext.cpp:938: Installing audio failed retrying...
   0.993 errno: 16 -- Device or resource busy

   0.993 Failed to init OSS.

   0.994 No audio driver can be used. (error code: 1)

   0.994 Warning GlobalContext.cpp:938: Installing audio failed retrying...
   1.494 errno: 16 -- Device or resource busy

   1.494 Failed to init OSS.

   1.494 No audio driver can be used. (error code: 1)

   1.494 Warning GlobalContext.cpp:938: Installing audio failed retrying...
   1.994 errno: 16 -- Device or resource busy

   1.994 Failed to init OSS.

   1.994 No audio driver can be used. (error code: 1)

   1.994 Warning GlobalContext.cpp:938: Installing audio failed retrying...
   2.495 errno: 16 -- Device or resource busy

   2.495 Failed to init OSS.

   2.495 No audio driver can be used. (error code: 1)

   2.495 Warning GlobalContext.cpp:938: Installing audio failed
   3.062 Loading mod core 0.0.0 (data.lua)
   3.137 Loading mod base 0.17.4 (data.lua)
   3.336 Loading mod base 0.17.4 (data-updates.lua)
   3.428 Checksum for core: 3928040144
   3.428 Checksum of base: 60305742

Yes, the audio device fails to initialise. But that also happened before 0.17, and it had never been a problem.

I had deleted all the user files and the basic files (i.e. uninstall/reinstall) before this. But the problem persisted before and after deleting the files.

[Oxyd]

How long have you waited for it to load? Does it use up CPU when it stops or does it just sit there idle?

[Svip]

I've tried letting it run for a few minutes, but to no avail.

Observing the process specifically doing start up, it gets its CPU usage almost up to 40% and stops at 15% or 29% (I can't tell when it's going to be one or the other, but the ultimate result is the same), it then drops to 0%, with a CPU time of 0:00.92. Then after a few seconds, it uses another 0.01 CPU time, after which it never uses any CPU, and its CPU time remains 0:00.93 after several minutes.

It seems to be that it's waiting for something, like an I/O issue. But the logs don't give any hint as to what it could be. And like I said, I tried clearing all my files and re-installing both program files and user files anew.

EDIT: Did my test a few more times, the total CPU time varies between 0:00.90 and 0:00.93, but I guess it just depends on other load factors anyway. The extra CPU time I saw happening later is from when I click ALT+F4 to close the program, so it at least somewhat handles the SIGTERM, but it doesn't actually close. Eventually my window manager asks whether I want to force close it.

Additionally, htop reports the state of the process at the time to be sleeping (S). So it isn't waiting for disk (that would be D).

[tehfreek]

Try putting it through `strace` to see where it gets stuck.

[Svip]

Since the binary `factorio` itself actually tells Steam to launch itself, I decided to close Steam and run Steam through `strace`. When I did that, Factorio started up entirely as I expected. To ensure this wasn't a case of 'observing the problem solves it', I closed Steam again, and opened it as I normally would. And Factorio starts up normally.

So it seems the issue has been solved, or at least been circumvented. It appears that Steam might have put itself in a weird condition that caused Factorio somehow not to get permission to build prototypes or access files or whatever. Then again, I've been seeing Civ6 acting up when I close it, with the process just running forever.

I assume the solution was to just restart Steam.

I can give you this much from strace:

Code: Select all

   3.455 Checksum of base: 3541142062
[0306/233556.596676:INFO:crash_reporting.cc(265)] Crash reporting enabled for process: renderer
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
JS method call WebChat.GetOverlayChatBrowserInfo with 1 arguments
JS method call Storage.SetString with 2 arguments
   3.882 Info PlayerData.cpp:69: Local player-data.json unavailable
   3.882 Info PlayerData.cpp:72: Cloud player-data.json available, timestamp 1529097112
   3.935 Crop bitmaps.

The "Checksum of base" line is usually where it ended before (according to the log). The four following lines appear to be from Steam. So it may have been when Steam attempts to insert its overlay that it got Factorio stuck in a rut.

[posila]

Well, I am glad the game works for you now.
Moving the thread to 1/0 magic