All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101834] WebGL shaders cause system freeze
Date: Wed, 19 Jul 2017 00:58:11 +0000	[thread overview]
Message-ID: <bug-101834-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1135 bytes --]

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

            Bug ID: 101834
           Summary: WebGL shaders cause system freeze
           Product: Mesa
           Version: 17.1
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: grmat@sub.red
        QA Contact: dri-devel@lists.freedesktop.org

Hardware:
Radeon R9 290X (Hawaii)

Installed components:
Linux 4.11.9
Libdrm 2.4.81
Mesa 17.1.4

Running Arch Linux, using both radeon and amdgpu drm drivers, Chromium and
Firefox the system can freeze when running WebGL shaders. I've experienced this
on shadertoy.com before and now have a reproducible example:

https://threejs.org/examples/webgl_gpgpu_protoplanet.html

Sound keeps on playing and I can move the cursor but not interact with the
system any more. If I can provide any logs to help, please ask.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2565 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

                 reply	other threads:[~2017-07-19  0:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-101834-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.