[Mesa-dev] [Bug 91687] Crash when creating new context after destroying the old one using indirect rendering

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91687

GitLab Migration User  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEEDINFO|RESOLVED

--- Comment #7 from GitLab Migration User  ---
-- 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/991.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 91687] Crash when creating new context after destroying the old one using indirect rendering

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91687

Timothy Arceri  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #6 from Timothy Arceri  ---
Is this working for you with recent Mesa? I was unable to figure out the
examples dependences on my distro so couldn't test.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 91687] Crash when creating new context after destroying the old one using indirect rendering

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91687

Marius Cirsta  changed:

   What|Removed |Added

 CC||mfor...@gmail.com

--- Comment #5 from Marius Cirsta  ---
 Happened to me with KDE too.

Thread 1 (Thread 0x7f9b04e05800 (LWP 1082)):
[KCrash Handler]
#6  0x7f9aea533a09 in update_framebuffer_state () from
/usr/lib/dri/r600_dri.so
#7  0x7f9aea53282c in st_validate_state () from /usr/lib/dri/r600_dri.so
#8  0x7f9aea53a5d1 in st_Clear () from /usr/lib/dri/r600_dri.so
#9  0x7f9b14f8b156 in QSGBatchRenderer::Renderer::renderBatches() () from
/usr/lib/libQt5Quick.so.5

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 91687] Crash when creating new context after destroying the old one using indirect rendering

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91687

--- Comment #2 from Guilherme gqm...@gmail.com ---
Created attachment 117785
  -- https://bugs.freedesktop.org/attachment.cgi?id=117785action=edit
xtrace with glx commands

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 91687] Crash when creating new context after destroying the old one using indirect rendering

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91687

--- Comment #3 from Guilherme gqm...@gmail.com ---
As the crash is a seg fault on update_framebuffer_size because surface=NULL, I
tried to just make a check if the surface is NULL. Then it does not crash
anywhere else, but nothing is rendered.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 91687] Crash when creating new context after destroying the old one using indirect rendering

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91687

Bug ID: 91687
   Summary: Crash when creating new context after destroying the
old one using indirect rendering
   Product: Mesa
   Version: 10.5
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: critical
  Priority: medium
 Component: Mesa core
  Assignee: mesa-dev@lists.freedesktop.org
  Reporter: gqm...@gmail.com
QA Contact: mesa-dev@lists.freedesktop.org

Created attachment 117783
  -- https://bugs.freedesktop.org/attachment.cgi?id=117783action=edit
VTK/Qt Python program that crashes

I tested that on mesa Ubuntu 14.04 (mesa 10.3.2) and 15.10 (mesa 10.5.2). I'm
not sure if it is reproducible. The attached traces were gotten on Ubuntu
14.04.

The crash happens when running the attached python program crash_mesa_vtk_qt.py
using indirect rendering (specifically I need to run it inside a chroot that
has a very old mesa version)

It uses vtk and Qt, I'm sorry I could not come up with a more isolated example,
but I'm not very familiar with opengl programming.


In summary, that is what is happening:

1 - A vtk render window is created and rendered the first time (that makes vtk
create a new glx context)

2 - The vtk render window is set to render offscreen (it is not using OSMesa).
That makes vtk destroy the current context and create a new one associated to a
new X offscreen window.

3 - The window is rendered and I could even generate a png file.

4 - The vtk render window is set to render on screen again. That makes vtk
destroy the current glx context and create a new one associated to the first X
window (the on screen window).

5 - When rendering the vtk window again, X server crashes (stack trace
attached).


Looking into vtk code it does not seem it is doing anything wrong. The
offscreen related code can be found on:

https://gitlab.kitware.com/vtk/vtk/blob/v6.2.0/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx#L800

https://gitlab.kitware.com/vtk/vtk/blob/v6.2.0/Rendering/OpenGL/vtkOpenGLRenderWindow.cxx#L1856

https://gitlab.kitware.com/vtk/vtk/blob/v6.2.0/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx#L943

https://gitlab.kitware.com/vtk/vtk/blob/v6.2.0/Rendering/OpenGL/vtkOpenGLRenderWindow.cxx#L1856

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 91687] Crash when creating new context after destroying the old one using indirect rendering

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91687

--- Comment #1 from Guilherme gqm...@gmail.com ---
Created attachment 117784
  -- https://bugs.freedesktop.org/attachment.cgi?id=117784action=edit
gdb stack trace

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev