Bug 100425 - glGenFramebuffersEXT appears to be null on (some?) Mesa 12.0.6 systems
Summary: glGenFramebuffersEXT appears to be null on (some?) Mesa 12.0.6 systems
Status: RESOLVED WONTFIX
Alias: None
Product: Mesa
Classification: Unclassified
Component: GLX (show other bugs)
Version: 12.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-28 00:18 UTC by Kai Ninomiya
Modified: 2017-03-28 21:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Kai Ninomiya 2017-03-28 00:18:20 UTC
Chromium is seeing GPU process crash reports on Linux with Mesa 12.0.6 in which the function glGenFramebuffersEXT appears to be null. This is seen on Intel mostly, some NVIDIA and a few AMD.

We have not tried to reproduce it as we don't have such a system on hand (sorry). It may be reproducible by running Chrome 57.0 Stable (snapshot below) on a Mesa 12.0.6 system and using WebGL 2.0: http://webglreport.com/?v=2 . See chrome://gpu for GPU process logs.
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/444952/ (chrome-linux.zip)

The glGenFramebuffersEXT call in question:
https://chromium.googlesource.com/chromium/src/+/57.0.2987.110/gpu/command_buffer/service/feature_info.cc#872

Here is the generated code for retrieving glGenFramebuffersEXT. Note that it should be requesting "glGenFramebuffers" on GL 3.0+.
https://cs.chromium.org/chromium/src/ui/gl/gl_bindings_autogen_gl.cc?l=1206&rcl=57.0.2987.110

GetGLProcAddress calls g_get_proc_address:
https://cs.chromium.org/chromium/src/ui/gl/gl_implementation.cc?l=126&rcl=57.0.2987.110

Which should be glXGetProcAddress on Linux:
https://cs.chromium.org/chromium/src/ui/gl/init/gl_initializer_x11.cc?l=58&rcl=57.0.2987.110
Comment 1 Timothy Arceri 2017-03-28 02:01:06 UTC
Does it happen on more recent Mesa releases? The 12.0 release is no longer supported.
Comment 2 Kai Ninomiya 2017-03-28 02:19:05 UTC
We don't see any reports on any versions other than 12.0.6, pretty much just on Ubuntu. These users appear to be on Ubuntu 16.04 LTS (xenial + xenial-updates). Unfortunately, we can expect that version to hang around for a while (being an LTS).
Comment 3 Timo Aaltonen 2017-03-28 07:36:03 UTC
fwiw, 17.0.x backport to xenial-updates is being prepared on a ppa:

https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates

so if the update fixes this bug then assume it's going to be on xenial within a few months.
Comment 4 Kai Ninomiya 2017-03-28 17:29:49 UTC
Thanks Timothy and Timo, if this isn't a major, widely-seen regression in 12.0.6 then there isn't much we can do. If Chromium added a workaround it would also be a few months before the fix is out, so the xenial-updates push will be best.

I'm fine with marking WONTFIX.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.