From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 63051] New: Displist with multiple OpenGL contexts crashes.
Date: Wed, 03 Apr 2013 01:50:53 +0000 [thread overview]
Message-ID: <bug-63051-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1483 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63051
Priority: medium
Bug ID: 63051
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: Displist with multiple OpenGL contexts crashes.
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: ideasman42-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: 9.1
Component: Drivers/DRI/nouveau
Product: Mesa
Created attachment 77349
--> https://bugs.freedesktop.org/attachment.cgi?id=77349&action=edit
open this file in blender2.66a, Press '1' key, to crash.
This is a bug we had reported in blender (3d modeling application).
But which I tracked down to being a crash in:
/usr/lib/xorg/modules/dri/nouveau_dri.so
The crash is caused by calling glCallList() when there are multiple windows
sharing the same opengl context.
(single window doesn't crash for example and removing use of display-lists in
the code also works).
I did some more tests and using Mesa-SoftwareGL doesn't crash, using NVidia
closed-source drivers.
Attached blend file to reproduce the crash, just run...
./blender displist_crash.blend
... then press ONE-Key, over either of the windows to see crash.
If you close a window before pressing ONE, it works without crashing.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2931 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2013-04-03 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 1:50 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-63051-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-02-05 8:21 ` [Bug 63051] Displist with multiple OpenGL contexts crashes bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-23 7:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-23 8:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-63051-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.