From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109229] glLinkProgram locks up for ~30 seconds
Date: Sat, 05 Jan 2019 10:45:23 +0000 [thread overview]
Message-ID: <bug-109229-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1080 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109229
Bug ID: 109229
Summary: glLinkProgram locks up for ~30 seconds
Product: Mesa
Version: 18.3
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: bronsonmathews@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
A recent updated to Manjaro/Arch has caused the Godot Engine to lock up when it
calls glLinkProgram.
This appears to be a Mesa 18.3 bug as the issue has started recently and so has
18.3 been rolled out recently in Manjaro.
Here are URL's to bug reports on the Godot forum that should provide further
information:
https://github.com/godotengine/godot/issues/24362
https://github.com/godotengine/godot/issues/24783
https://github.com/godotengine/godot/issues/24340
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2635 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:[~2019-01-05 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 10:45 bugzilla-daemon [this message]
2019-01-07 1:31 ` [Bug 109229] glLinkProgram locks up for ~30 seconds bugzilla-daemon
2019-01-07 21:07 ` bugzilla-daemon
2019-01-08 0:01 ` bugzilla-daemon
2019-01-08 1:49 ` bugzilla-daemon
2019-01-08 23:50 ` bugzilla-daemon
2019-01-11 5:13 ` bugzilla-daemon
2019-01-17 1:50 ` bugzilla-daemon
2019-01-28 6:17 ` 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-109229-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.