[0.11.12][OSX] Crash on DNS-Error

Bugs that we were not able to reproduce, and/or are waiting for more detailed info.
Post Reply
DSchmidtberg
Burner Inserter
Burner Inserter
Posts: 5
Joined: Fri Dec 18, 2015 5:08 pm
Contact:

[0.11.12][OSX] Crash on DNS-Error

Post by DSchmidtberg »

0.000 2015-12-18 18:12:27; Factorio 0.11.22 (Build 14011, mac)
0.000 Operating system: Mac OS X 10.11.2
0.000 Read data path: /Applications/factorio.app/Contents/data
0.000 Write data path: /Users/<USER>/Library/Application Support/factorio
0.000 Binaries path: /
1.389 Graphics options: [FullScreen: true] [VSync: true] [UIScale: 100%] [MultiSampling: OFF] [Graphics quality: normal] [Video memory usage: all]
1.450 Loading mod core 0.0.0 (data.lua)
1.468 Loading mod base 0.11.22 (data.lua)
1.779 Loading mod base 0.11.22 (data-updates.lua)
2.541 Initial atlas bitmap size is 16384
2.545 Created atlas bitmap 16384x6553
12.319 Info Updater.cpp:717: Downloading https://www.factorio.com/updater/get-av ... iVersion=2
22.324 Info Updater.cpp:727: Download failed (Couldn't resolve host name -- name lookup timed out)
22.372 Factorio initialised
Factorio crashed. Generating symbolized stacktrace, please wait ...
Couldn't symbolize stacktrace: (resolving symbol failed: fread)
22.663 Error Util.cpp:43: Unexpected error occurred. You can help us to solve the problem by posting the contents of the log file on the Factorio forums.
dig http://www.factorio.com

; <<>> DiG 9.8.3-P1 <<>> http://www.factorio.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6029
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.factorio.com. IN A

;; Query time: 2998 msec
;; SERVER: <IPv4>#53(<IPv4>)
;; WHEN: Fri Dec 18 18:00:14 2015
;; MSG SIZE rcvd: 34

User avatar
HanziQ
Former Staff
Former Staff
Posts: 630
Joined: Fri Mar 27, 2015 7:07 am
Contact:

Re: [0.11.12][OSX] Crash on DNS-Error

Post by HanziQ »

This is from an old Factorio version, if this wasn't a one-time thing and it still happens in the new stable version - 0.12, please report it again.

Also the dig output seems to be correct.

Post Reply

Return to “Pending”