New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Steam client][Waveform] Waveform segmentation faults when Steam overlay appears #548
Comments
Just found this one: #31. I'd want to remark that the crash happens even executing everything without using |
As I said on #230, try disabling the overlay in your steam settings and let us know if it works. |
Disabling the in-game Steam community I do not incur in crashes anymore (so the problem seem to be definitively bound to the overlay). BTW a focus stealing on achievements happens (#156), with the game getting paused and exiting the full screen mode (but no crash, according to this comment this should be fixed in the next release). I'm on Xubuntu 12.10 (XFCE4 with compositing disabled).
|
I can run Waveform with the overlay without a problem. A new steam client was just released, does that fix this problem? |
Also happens on my system: Información sobre el procesador: Información sobre la red: Versión de Windows: Tarjeta de vídeo:
Tarjeta de sonido: Memoria: Varios: And mind you, I have almost EXACTLY the same laptop as the bugreporter, but mine is an K53SD (GeForce 610M instead of a 540M), and I'm running Debian Wheezy. Here is what it happens here:
|
The Steam client update did not help me either, Waveform keeps crashing when community overlay is active. BTW, @dilworks' issue is different from mine: I can play Waveform without any crash when the Steam community is disabled, apart from one while exiting the game, which I don't know if it is related to this.
Resuming:
|
OK, thanks for checking. |
Waveform Steam is currently in the middle of a confusing war with the overlay and the Intel driver. Eden and I are pretty sure it's the engine's stack allocator messing with the Intel driver's memory management. I'm still working on a fix, but testing is very much appreciated: http://flibitijibibo.com/waveformLinux.tar.bz2 Basically just trying to run the game without the allocator, among other minor fixes. As for the fullscreen focus, we've been getting that error with a number of SDL 1.2 games. Various devs are looking at this separately. |
Tried the test... Still crashes with overlay enabled. With it disabled, I can now go in-game with Intel drivers, but it again crashed on me after finishing a level, after the score displays. |
If you can grab backtraces I may be able to fix it... removing the allocator made things a bit unstable, so I'm sure there are crashes still in the game, particularly between game states. |
Wonderful. It's now crashing when I try to start a game! Not always, but most of the times it dies after trying to start a game. Steam overlays still disabled. Hooked the thing to GDB, here are a couple of backtraces:
After a rough road of crashy-crashy runs, I managed to pick my savegame and play a entire stage. Then, after the score screens... another crash. But the backtrace here looks very different:
Hope this helps! |
Well, the good news is that it's no longer anything ugly with the driver. The problem at this point seems to be things in the actual Waveform engine. May just need to spend a few more nights with this and Valgrind, but I've sent this thread to Eden in case they have any ideas. |
Oh, hey, weird thing: Delete libstdc++.so.6 from Waveform/x86/. I wonder if it's conflicting with the libs in .steam/bin/? |
No difference. Actually, there is not even a libsdtc++.so inside Steam libs (At least on my setup), it just defaults to Debian's libstdc++. But hey, nice to know that Sandy Bridge doesn't hate Waveform :) |
Hm. I wonder what that ~/.steam/lib/ deal is, anyway... Thanks for the backtraces, though. I don't know for sure how long it'll take to get Waveform working without its custom stack allocator, but we're looking at it. |
I tried the binaries you provided. Good news and bad news. The game does not crashes anymore opening the Steam overlay, but it leaves the screen completely corrupted (with my use photo stretched to the whole screen). Something similar happens with World of Goo too.
which seems not to be related with this bug (but reading previous comments it is something expected). Deleting `./x86/libstdc++.so.6 did not helped:
I then deleted
It seems you are working on the right bits... :) |
Updated the waveformLinux archive. I don't think this does anything to deter the free() issues, but I've changed enough back here to make it worth trying out anyway. |
Still crashy-crashy. The backtrace isn't different at all (still dies on a free()). But hey, at least the Steam overlay isn't being guilty this time... because it still crashes on the same points, just no more after unlocking an achievement. |
Does it happen to die on the same functions too? I did end up fixing a few |
Updated the archive again. Lots of Valgrind fixes, but I need every backtrace I can possibly get. Get every Intel user you know to try this binary out; if they need a demo version I can supply a beta build of that too. |
OK, since you want backtraces, how about ~10 of 'em? The good news: If you can get it running past the titlescreen, it won't crash anymore at exit, yay! The bad news: It crashes just after clicking "Play" if launched from Steam, meaning that it's unplayable. It seems that Waveform doesn't want to play with Steam's libc.so.6 under Wheezy. Overlay or no overlay makes no difference. If started standalone from a console, it works. I can't provide with backtraces, since Waveform dies with a SIGTRAP after hooking to it in gdb, hence no backtrace options for a dead process. The somewhat-ugly news: I've tested under KDE4 and MATE - Waveform seems to be more stable under MATE (as in "almost rock solid!"), while it behaves a bit crashy under KDE4(.8.4). Disabling desktop effects does nothing. |
Excellent. Also kind of glad to see it's all in the same set of places... I wonder why Wheezy is getting that behavior, too. The desktop differences are also interesting... I'm usually working on Fedora, currently on Cinnamon but previously Gnome 3, and I've had a tough time reproducing these... though a lot of it is still us fighting with the hardware. I may also just disable that blasted launcher... it's nothing but trouble on every platform, as far as I can tell. |
Actually, just to be sure: Are you referring to "Play" after the launcher (silent black screen with Waveform logo) or at the title screen (animated title with music)? EDIT: What was I thinking, Launcher uses "Start"... Also, the libc thing may be something out of my control if it's specific to Steam. Is @gdrewb-valve still around? |
I'm still here. What libc thing do you mean? |
You'd have to ask @dilworks for the specifics... it sounds like something you have to observe first-hand. Also, sorry for the confusion with the menu buttons. Had to open the launcher again to see that the button names are totally different. |
@flibitijibibo: It's the one on the animated title screen. @gdrewb-valve: I did my initial install of Steam under Wheezy using (a slighty older version of) this script: http://kanotix.com/files/fix/install-steam-wheezy.sh |
Thanks for the info, the need for a newer libc for Steam isn't surprising, and not likely to change. |
Updated the archive one more time. Disables the launcher, because my crash rate goes down about 95% with it off. Unfortunately there's going to be a point where I have to stamp a release tag on this regardless of error rate, because I'm going to have to rush my next port with each minute I spend on bugfixes for old ones. A downside to being a porter of many games. :/ The key things are there though. The game should never ever crash on Steam or Intel GPU routines. |
Neat! More stable than ever. It still crashes, but at least the frequency is MUCH lower. Nearly rock-solid if started standalone, and actually playable if started from Steam. However, this time I'm on MATE... Will try later under KDE4, but it's looking very good. |
Closing as this appears mostly resolved. |
When Waveform is launched from within the Steam client, it crashes whenever the Steam overlay appears (i.e. hitting Shift+TAB or getting an achievement). Log:
I'm on Xubuntu 12.10 + nvidia-experimental-310 on an Asus X53SV (AKA K53SV). The crash happens no matter the video card used (plain Intel or Nvidia 540M via optirun or primusrun).
Running the application directly from the terminal workarounds the issue (no Steam overlay).
Problems with
gameoverlayrenderer.so
seem quite common...The text was updated successfully, but these errors were encountered: