When resizing opengl-application's window size > 2048, this results in a hard system crash (num-lock not working, sound-card playing buffer again and again). OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) 945GM x86/MMX/SSE2 OpenGL version string: 1.4 Mesa 7.12-devel (git-44c65d0) Kernel: 3.1.0-5.fc16.i686 xorg-server: 1.11.1 intel-ddx: 2.16.901 (SNA)
Tried to get a stacktrace with gdb, however because my laptot seems to completly die I can't get any further information. Is there any additional information I can provide to help get this bug fixed?
If I resize glxgears beyond 2048, all I get is an invalid DRI drawable and glxgears crashes. Nothing more sinister. Might want to try a few different kernels to see if there is one that doesn't hard lock, otherwise netconsole might capture something.
just tested, doesn't happen with mesa-7.11 shipped with Fedora 16, but I still experience it with linux-3.1.1 and mesa-7.12 git.
still there with linux-3.1.4 and Mesa 7.12-devel (git-d958202)
crash seems to be fixed with Mesa 8.0-devel (git-189e6c7) :) The only thing I get when using windows with >2048 is broken geometry and/or no rendering at all.
Created attachment 56759 [details] glxgears screenshot with >2048px
*** Bug 56585 has been marked as a duplicate of this bug. ***
(In reply to Clemens Eisserer from comment #5) > crash seems to be fixed with Mesa 8.0-devel (git-189e6c7) :) > > The only thing I get when using windows with >2048 is broken geometry and/or > no rendering at all. Assumable fixed with latest SW? Could you confirm. Otherwise closing soon. Thank you.
-- 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/701.
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.