Segfault on GNU/Linux

[DrMcCoy]

Like for others, Wasteland 2: Director's Cut crashes for me. It happens right at the start, after showing the first loading title screen thing for a few seconds.

The Unity3D Player.log contains a stacktrace, but since the binary's stripped, it might not be all that useful: https://gist.github.com/DrMcCoy/35143a7f31ef75b3cfdc

Obviously, I can't force it to use Direct3D 9 on GNU/Linux, so this workaround is a non-starter for me.

While I didn't expect much trying to run it in gdb or valgrind (since it's stripped, and following C# is not really great), I noticed that you're raising SIGPWR and SIGXCPU a whole lot (EDIT: Ah, apparently, that's some internal hackery mono does). Running it in valgrind even makes it kill itself before creating a window.

EDIT: Calling mono_pmip() in gdb of all the addresses in the callstack produces nothing.

[winterheart]

Same problem.
Here my thread in off-site: https://forums.inxile-entertainment.com/viewtopic.php?f=34&t=13974

[empty_hat]

Same issue as well.

[Hyper_Eye]

I have the same problem. If I start the game from outside of Steam I get past the initial loading screen but after I select my squad it crashes on the subsequent loading screen.

I'm running Gentoo amd64 with an Nvidia GTX 670.

[sunshinecorp]

On Ubuntu 12.04.5 64-bit and AMD A10-5800K APU (AMD Radeon HD 7660D) running latest 15.9 Catalyst proprietary drivers. Crashes for me as well, on first loading screen.

Player.log here:

http://pastebin.com/G1nKdMen

[Tumocs]

Same problem.
Player log http://pastebin.com/pweNvNpb
Archlinux 64bit kernel 4.2
amd r7 260x with mesa 11.0

EDIT: -screen-fullscreen 0 in launch options let me start the game. Now we'll see if can get in to the game itself.

EDIT2: seems to work fine in windowed mode.

[DrMcCoy]

-screen-fullscreen 0 still crashes for me

[sunshinecorp]

Yeah, switching manually to windowed mode DOES work for me, which makes me notice a whole new problem now. :) While the original Wasteland 2 was running fine after a few patches (it was sluggish at release, then over time they made it run faster and faster) the DC version is sluggish once again, even on the lowest setting of graphics. Well, I suppose I just have to be patient and wait for optimizations to come though.

[superjamie]

inXile are aware of this and are working to resolve it. See my response in this thread:
https://steamcommunity.com/app/404730/discussions/1/481115363877882363/

[Evgueni [Linux user]]

Not exactly crashes but freezes when entering to a new location.

Here there is a workaround (for Linux users only and may be Mac ?). They say that it is also helped for crashes and load game problem.

It looks like the game open a lot of files simultaneously so it hits the current ulimit

Was:
> ulimit -n
1024

After adding the following lines into /etc/security/limits.conf (read the comments in the file for understanding what happening):

# due to wasteland2
YourLoginName soft nofile 4096
YourLoginName hard nofile 8192

After relogin:
> ulimt -n
4096

And the game runs more or less smoothly. It is obviously a game bug.

[Slayer Sam]

Evgueni nailed it !

This workaround fixed all my crashyness and what appeared like corrupted savegames and whatnot. (Linux)

I hope the devs are reading this.

[superjamie]

What Evgueni describes is a different issue to the segfault on launch.

[superjamie]

WL2DC updated today, this is fixed for me now.

[Heavyimpcat]

helped me on Director Cut GOG version of game too. thanks