You can sign up to get a daily email of our articles, see the Mailing List page!
  Go to:
Everspace suddenly crashing
naegling23 commented on 19 October 2019 at 12:54 pm UTC

The game has worked for a while, but now I cant get it to launch. It crashes when the menu screen loads.
4.17.2-0+++UE4+Release-4.17 513 0
Disabling core dumps.
Setting breakpad minidump AppID = 396750
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198084045019 [API loaded no]
CAppInfoCacheReadFromDiskThread took 12 milliseconds to initialize
CApplicationManagerPopulateThread took 195 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
RecordSteamInterfaceCreation (PID 21995): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 21995): SteamUtils008 / Utils
RecordSteamInterfaceCreation (PID 21995): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 21995): SteamUtils008 / Utils
RecordSteamInterfaceCreation (PID 21995): SteamNetworking005 / Networking
RecordSteamInterfaceCreation (PID 21995): SteamGameServerStats001 / GameServerStats
RecordSteamInterfaceCreation (PID 21995): STEAMHTTP_INTERFACE_VERSION002 / HTTP
RecordSteamInterfaceCreation (PID 21995): STEAMINVENTORY_INTERFACE_V001 / Inventory
RecordSteamInterfaceCreation (PID 21995): STEAMUGC_INTERFACE_VERSION009 / UGC
RecordSteamInterfaceCreation (PID 21995): STEAMAPPS_INTERFACE_VERSION008 / Apps
Unable to read VR Path Registry from /home/naegling23/.config/openvr/openvrpaths.vrpath
Unable to read VR Path Registry from /home/naegling23/.config/openvr/openvrpaths.vrpath
malloc(): memory corruption (fast)
Signal 11 caught.
Signal 6 caught.
Signal 11 caught.
Signal 11 caught.
Malloc Size=131076 LargeMemoryPoolOffset=131092
CommonLinuxCrashHandler: Signal=6
Malloc Size=65535 LargeMemoryPoolOffset=196655
Segmentation fault (core dumped)



I reached out on the steam forums, but it looks like the developer cant help me with this issue and there are too few linux gamers hanging around that forum. Figured this would be the next best place to try. The steam forum link is here
https://steamcommunity.com/app/396750/discussions/1/1628539187775661575/

Liam Dawe commented on 19 October 2019 at 1:44 pm UTC

I assume you've verified the game files on Steam to be sure?

What distro is this? GPU? Driver version?

If you want help, you need to give us basic details about your system.

Mine continues to load fine on Steam, I get this up until the main menu:

Quote[liam@liam-manjaro ~]$ /media/storage/SteamLibrary/steamapps/common/EVERSPACE/EverspaceWithSystemLibraries.sh
4.17.2-0+++UE4+Release-4.17 513 0
Disabling core dumps.
Setting breakpad minidump AppID = 396750
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197987942764 [API loaded no]
CAppInfoCacheReadFromDiskThread took 39 milliseconds to initialize
RecordSteamInterfaceCreation (PID 24923): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 24923): SteamUtils008 / Utils
RecordSteamInterfaceCreation (PID 24923): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 24923): SteamUtils008 / Utils
RecordSteamInterfaceCreation (PID 24923): SteamNetworking005 / Networking
RecordSteamInterfaceCreation (PID 24923): SteamGameServerStats001 / GameServerStats
RecordSteamInterfaceCreation (PID 24923): STEAMHTTP_INTERFACE_VERSION002 / HTTP
RecordSteamInterfaceCreation (PID 24923): STEAMINVENTORY_INTERFACE_V001 / Inventory
RecordSteamInterfaceCreation (PID 24923): STEAMUGC_INTERFACE_VERSION009 / UGC
RecordSteamInterfaceCreation (PID 24923): STEAMAPPS_INTERFACE_VERSION008 / Apps
CApplicationManagerPopulateThread took 8868 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
Unable to read VR Path Registry from /home/liam/.config/openvr/openvrpaths.vrpath
Unable to read VR Path Registry from /home/liam/.config/openvr/openvrpaths.vrpath

Is this with or without the Encounters DLC?

naegling23 commented on 19 October 2019 at 2:08 pm UTC

sure, forgot about that
Ubuntu 19.04 8gb ram (system is showing 7.7),Intel® Core™ i5-4590 CPU @ 3.30GHz × 4 , nvidia gtx 750ti running 418.56 drivers. 32gb swap memory.

I have uninstalled and reinstalled the game as well.

Liam Dawe commented on 19 October 2019 at 2:16 pm UTC

Well, for starters the 418.56 driver is outdated by about 7 months, you should look to upgrade to a much more recent driver and re-test.

I have absolutely no issues on Manjaro with the 430.40 drivers.

naegling23 commented on 19 October 2019 at 4:40 pm UTC

upgraded to 430 drivers, same problem:
4.17.2-0+++UE4+Release-4.17 513 0
Disabling core dumps.
Setting breakpad minidump AppID = 396750
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198084045019 [API loaded no]
CApplicationManagerPopulateThread took 51 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
RecordSteamInterfaceCreation (PID 6771): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 6771): SteamUtils008 / Utils
RecordSteamInterfaceCreation (PID 6771): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 6771): SteamUtils008 / Utils
RecordSteamInterfaceCreation (PID 6771): SteamNetworking005 / Networking
RecordSteamInterfaceCreation (PID 6771): SteamGameServerStats001 / GameServerStats
RecordSteamInterfaceCreation (PID 6771): STEAMHTTP_INTERFACE_VERSION002 / HTTP
RecordSteamInterfaceCreation (PID 6771): STEAMINVENTORY_INTERFACE_V001 / Inventory
RecordSteamInterfaceCreation (PID 6771): STEAMUGC_INTERFACE_VERSION009 / UGC
RecordSteamInterfaceCreation (PID 6771): STEAMAPPS_INTERFACE_VERSION008 / Apps
CAppInfoCacheReadFromDiskThread took 871 milliseconds to initialize
Unable to read VR Path Registry from /home/naegling23/.config/openvr/openvrpaths.vrpath
Unable to read VR Path Registry from /home/naegling23/.config/openvr/openvrpaths.vrpath
Signal 11 caught.
Malloc Size=131076 LargeMemoryPoolOffset=131092
CommonLinuxCrashHandler: Signal=11
Malloc Size=65535 LargeMemoryPoolOffset=196655
Signal 11 caught.
Segmentation fault (core dumped)

naegling23 commented on 24 October 2019 at 9:41 pm UTC

just an FYI, I tried switching to the non-beta steam, still crashes, so I dont think its a steam issue from what I can tell.

Ehvis commented on 25 October 2019 at 8:22 am UTC

Log suggests it is related to memory allocations. Have you tested your memory lately?

naegling23 commented on 26 October 2019 at 6:55 pm UTC

I ran memtes, it checked out fine. I have 8gb, the system monitor is telling me 7.7. I was planning on upgrading to 16gb in the near future, so maybe that would help, but Its frustrating that it used to work fine.

naegling23 commented on 27 October 2019 at 5:12 pm UTC

game appears to be working now. I managed to start the game, turn all the settings down to low (they were set to epic despite lowering them manually). I exited the game then successfully restarted it. How did I fix it you ask? I upgraded to 19.10 (im on budgie). I have no clue why this did anything, in fact the install crashed in the middle of the update so I expected to have problems. I'll post again next week when I discover that some other game randomly stopped working...but thanks for everyone's help.

tuxintuxedo commented on 27 October 2019 at 8:58 pm UTC

Although it's not an all-purpose magic trick, I would advise using an LTS version. With HWE enabled you won't really lose performance and you get a more stable experience. From what you wrote it seems like some kind of bug that was fixed in the next version.

naegling23 commented on 27 October 2019 at 9:59 pm UTC

Thats been my plan, just waiting for the next LTS before I settle down. I started with ubuntu at warty/breezy, so I had it ingrained that each new release added a ton of features, but I finally realized a couple months ago that its no longer the case. I'll be sticking to the LTS releases starting at the next one, I dont have any intention on downgrading at this point.

  Go to:

You need to Register and Login to comment, submit articles and more.


Or login with...

Livestreams & Videos
None currently, submit yours here!
See more!
Popular this week
View by Category
Contact
Latest Comments
Latest Forum Posts