Factorio Forums

A great honor to post the first bugs

Started the game 2 times, got 2 different errors I think, see logs.

Edit: For now the issue of the second log is handled here: 54548

I have the same problem on macOS, except, the game didn't produce a log for launching 0.16.

In addition, after the initial crash, the application doesn't launch anymore at all, the OS says the application can't be opened.

Did you guys do a clean install? Overwrite? Update?

SevenMass wrote:I have the same problem on macOS, except, the game didn't produce a log for launching 0.16.

In addition, after the initial crash, the application doesn't launch anymore at all, the OS says the application can't be opened.

Make a dedicated report please, follow: 3638.

Dev-iL wrote:Did you guys do a clean install? Overwrite? Update?

Did dirty steam update from 0.15.40 to 0.16.0.

Thanks for the report. Does it crash every time a the same place? Or was this a one-off thing?

Oh now it seems to work, I can get into my map and also start a new one.
Seems it was just the first 2 starts.

Update: Now it un-fixes itself again, get the loadBitmap error or artillery error at random, both at "loading sprites" between 40-69% so far. This last crash I didn't even get a message window and the window just closed, log attached.

What does your memory usage show as when you load the game?

I currently could only get the artillery error and not the loadBitmap error, but RAM seems to be the culprit (see image)

What do you have open that's consuming almost half of your RAM before even launching Factorio?

Mostly chrome with a dozen 9gag tabs and 1080p youtube running in another window. For the test in the image graph I also had the Overwatch menu started.

Update: 16.1 has the same problems for me, sometimes GDIPPreloadData error, sometimes train error, sometimes crash without error and now a new error saying my page file is too small (4GB). But all only if free RAM is getting low, the cached RAM seems to mostly stay untouched.

Ekelbatzen wrote:Update: 16.1 has the same problems for me, sometimes GDIPPreloadData error, sometimes train error, sometimes crash without error and now a new error saying my page file is too small (4GB). But all only if free RAM is getting low, the cached RAM seems to mostly stay untouched.

Kill the Chrome and start the game then?
You can relaunch it after

Basically game does huge mem usage spike on load now which your system doesn't cope well with. Having as much free memory will help and page file hints mean that Windows is running out of contiguos physical memory locations to reserve for Factorio.

That simply sounds like it's running out of RAM. You can disable the threaded sprite loading option in the config file (uncomment and change thread-sprite-loading to false) or let windows manage your page file size as you should.

orzelek wrote:

Ekelbatzen wrote:Update: 16.1 has the same problems for me, sometimes GDIPPreloadData error, sometimes train error, sometimes crash without error and now a new error saying my page file is too small (4GB). But all only if free RAM is getting low, the cached RAM seems to mostly stay untouched.

Kill the Chrome and start the game then?
You can relaunch it after

Basically game does huge mem usage spike on load now which your system doesn't cope well with. Having as much free memory will help and page file hints mean that Windows is running out of contiguos physical memory locations to reserve for Factorio.

Yeah I am ok with this or accepting longer load times, I just want to help the devs catch these kind of exceptions or make better error messages for other people who have no understanding for these kinds of things.

FYI 16.2 seems to have done the trick, I can start the game with 6,5/16gb ram reserved which i couldn't with 16.1 and 10/16gb also works.