I believe the problem is in the 358 drivers.
Well, on the one hand iirc the bug didn't happen before, but on the other hand I don't have any issues with those drivers. I've tried debugging but couldn't find any hint on whether it's the one or the other way ;/
The 358.x drivers are known to have issues affecting the Steam Client and other apps; it's unsupported with the Steam client and the 361 beta driver should be used instead.
Nothing extracted yet.
Rather 'randomly' steam crashes with SIGABRT when interacting with GUI elements (but also when it's running in background but the GUI is updated, eg. for notifications).
System Info:
One particular case with all logs I could gather:
writing minidumpin the log. Also I forgot to generate a core file)Last call by a steam program (complete backtrace here: https://gist.github.com/LeonardKoenig/c64f7dca6dc3047e73b7#file-bt):
The address where everything went wrong:
So we have an offset of
0x4581Cwhich gives us a base address of0x5BD9Cin thevgui2_s.so, which corresponds to this snippet:All logs etc:
https://gist.github.com/LeonardKoenig/c64f7dca6dc3047e73b7
Some other dumps / corresponding core files (created with breakpad minidump-2-core) I've found which seem to be related:
https://drive.google.com/file/d/0B2gXBp6AAG7fbkhEV3oxRkRRSTA/view?usp=sharing