All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 87568] WebGL can cause GPU reset
Date: Sun, 21 Dec 2014 21:57:55 +0000	[thread overview]
Message-ID: <bug-87568-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 87568
           Summary: WebGL can cause GPU reset
           Product: Mesa
           Version: 10.3
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: aaalmosss@gmail.com

I was given this link: http://hunger.hu/webgl.html which was supposed to crash
any video driver, and it really did a hiccup. Fortunately, after 1 second the
kernel detected GPU lockup, and reinitialized everything just fine.

As far as I can tell that javascript doesn't do anything sinister, just tries
to render 200k triangles with a single glDrawElements() call. Shouldn't there
be a protection against such simple overflows somewhere?

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

[-- Attachment #1.2: Type: text/html, Size: 2198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-12-21 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 21:57 bugzilla-daemon [this message]
2014-12-22 19:09 ` [Bug 87568] WebGL can cause GPU reset bugzilla-daemon
2014-12-24 14:21 ` bugzilla-daemon
2015-01-17  0:29 ` bugzilla-daemon
2019-09-18 19:18 ` 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-87568-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.