System Information Operating system: Linux-5.1.6-gnu-1-x86_64-with-arch 64 Bits (Parabola GNU/Linux-libre) arch derivative Graphics card: NV117 nouveau 4.3 (Core Profile) Mesa 19.1.0 description of error: Blender crash when opening the material tab in properties and opening preview tab this GPU ( nividia GTX 750Ti ) support OpenGL 4.3 on the nouveau and blender run fine but when opening material tab it crash. and here is glxinfo | grep OpenGL : OpenGL vendor string: nouveau OpenGL renderer string: NV117 OpenGL core profile version string: 4.3 (Core Profile) Mesa 19.1.0 OpenGL core profile shading language version string: 4.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.3 (Compatibility Profile) Mesa 19.1.0 OpenGL shading language version string: 4.30 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.1.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions:..... NOTE: also reported in https://developer.blender.org/T66159
Unfortunately blender can be very difficult to use for someone who has no idea about any of that stuff (like me). Can you make an apitrace which reproduces the crash when replayed? Failing that, can you provide idiot-proof instructions for how to trigger the crash, given that I don't know how to locate tabs in Blender, much less the "material" one? (I don't think I even have a copy of Blender installed either, and definitely low on disk space, so the apitrace way is much more likely to lead to an investigation and perhaps eventual fix.)
Created attachment 144648 [details] system hang
this bug hang my system and i can't even go to virtual terminal as it appear in the system hang attachment so i cant record apitrace because when i did that the trace file was corrupted and i cant replay it
Created attachment 144649 [details] Photo tutorial to reproduce the bug
I put photo tutorial to reproduce the bug in the attachment steps and arrange by their number from 1 to 8
Created attachment 144811 [details] This is an apitrace file for blender 2.8 rc1 This bug appear when using evee realtime rendering engine which is OpenGL 3.0+ application and seems that is require a lot of GPU power or maybe some OpenGL 3.0+ functionality in broken in Nouveau. any way here is the trace file.
(In reply to joinlaw from comment #6) > Created attachment 144811 [details] > This is an apitrace file for blender 2.8 rc1 > > This bug appear when using evee realtime rendering engine which is OpenGL > 3.0+ > application and seems that is require a lot of GPU power or maybe some > OpenGL 3.0+ > functionality in broken in Nouveau. > > any way here is the trace file. replaying this trace crashes glretrace. Can you verify that replaying the trace works for you? And what version were you using to record it?
anyway, I am able to trigger one issue in blender, not quite sure if this is the exact one. I don't even have to press this preview thing, just hovering over it is enough. Seems like the rendering engine on the GPU hangs...
(In reply to Karol Herbst from comment #7) > > replaying this trace crashes glretrace. Can you verify that replaying the > trace works for you? And what version were you using to record it? I use apitrace 8.0 and to replay the trace i use glretrace -b --sb blender.2.trace or i use qapitrace and uncheck all the checkboxes in retrace configuration in it to replay the trace. The trace is playing fine to me, but when i record it my whole system hang after opening material tab as described then i poweroff my computer and restart it and the trace file recorded.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1184.
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.