From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98293] Crash on Intel HSW when using multiple OpenGL contexts and X11 Display connections.
Date: Mon, 17 Oct 2016 13:06:30 +0000 [thread overview]
Message-ID: <bug-98293-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1254 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98293
Bug ID: 98293
Summary: Crash on Intel HSW when using multiple OpenGL contexts
and X11 Display connections.
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel@lists.freedesktop.org
Reporter: damian.dixon@gmail.com
I've looked at reassigning the following Mesa bug report to libdrm.
https://bugs.freedesktop.org/show_bug.cgi?id=91082
but I can't seem to do so, or what is more correct I don't know how too.
The following patch:
Fabrice Bellet, change to libDRM:
intel/intel_bufmgr_gem.c
https://bugs.freedesktop.org/attachment.cgi?id=122880
Fixes a crash I was seeing in Mesa when I have two threads, each with an X11
display connection and each with an OpenGL context.
Each context is tied to the X11 Display, they are not swapped or used from
another Display connection.
The only resource shared between the two contexts are texture IDs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2783 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-10-17 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 13:06 bugzilla-daemon [this message]
2016-10-17 13:07 ` [Bug 98293] Crash on Intel HSW when using multiple OpenGL contexts and X11 Display connections bugzilla-daemon
2016-11-02 6:49 ` bugzilla-daemon
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-98293-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.