Bug 100390

Summary: [steam] Grand Ages: Medieval crashes instantly
Product: Mesa Reporter: Christoph Berliner <caberliner>
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: NEW --- QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium CC: caberliner
Version: git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: crashlog
crashdump
glxinfo
basic system information

Description Christoph Berliner 2017-03-25 15:08:41 UTC
Created attachment 130451 [details]
crashlog

The Steam game Grand Ages:Medieval crashes instantly after startup.

Please tell me what further information you need, this is my first bug report.
Comment 1 Christoph Berliner 2017-03-25 15:09:36 UTC
Created attachment 130452 [details]
crashdump
Comment 2 Christoph Berliner 2017-03-25 15:11:57 UTC
Created attachment 130453 [details]
glxinfo
Comment 3 Christoph Berliner 2017-03-25 15:19:43 UTC
*** Bug 100388 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Berliner 2017-03-25 15:27:30 UTC
Created attachment 130454 [details]
basic system information
Comment 5 Christoph Berliner 2017-03-25 15:30:27 UTC
And probably a similar problem described in the steam community:

http://steamcommunity.com/app/221410/discussions/0/540743757387624740/
Comment 6 Samuel Pitoiset 2017-03-27 23:07:22 UTC
The game requests a 4.1 compatibility profile which is unsupported by Mesa and it crashes because it doesn't check the return value of glXCreateContextAttribsARB.

I'm investigating in order to know if it's possible to add a driconf option, but it looks like the game really needs some unsupported features.
Comment 7 Samuel Pitoiset 2017-03-27 23:57:11 UTC
Okay, the game uses ARB_texture_buffer_object which is only exposed with a core profile for some reasons. I'm able to run the game with some hacky changes but it fails to render correctly at some point.

Unfortunately, I don't think we can do anything for it because compat >= 3.1 is not supported for now (and probably won't be in the near future).

Anyways, the game should not crash when the returned context is NULL.
Comment 8 Christoph Berliner 2017-03-28 07:28:36 UTC
That doesn't sound to bad, does it?
At least it looks like the problem could be isolated.

Thanks and I'm happily trying fixes as long they're not exhausting my capabilities.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct.