Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 110500] X-Server crashes - GL error: GL_OUT_OF_MEMORY in glTexSubImage
Date: Sat, 04 May 2019 17:14:38 +0000	[thread overview]
Message-ID: <bug-110500-8800-dYVdeQAHpU@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110500-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #9 from Karol Herbst <karolherbst-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to wixbisce-jFQLhMmostjmZLV5cmOKUwC/G2K4zDHf@public.gmane.org from comment #7)
> I talked with a developer. I get told, that when a driver provide a
> functionality, that functionality should be working. They should be able to
> rely on a normal, expected functionality.
> 

I don't see how that is a Nouveau issue except somebody shows otherwise. Sure
Nouveau should be able to handle out of memory situations better, but the issue
here is, that glamor crashes. This is nothing Nouveau could prevent.

Anyway, ignoring that out of memory issue for now. It's not even proven that
the crash actually resulted from this out of memory error (even though it is
likely). Glamor tries to workaround it, but fails.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-05-04 17:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 15:34 [Bug 110500] New: X-Server crashes - GL error: GL_OUT_OF_MEMORY in glTexSubImage bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-110500-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-04-23 16:02   ` [Bug 110500] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-23 18:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-23 18:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-23 18:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-23 18:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-23 18:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-23 18:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-23 19:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-24 10:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-24 10:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-04 17:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-05-04 17:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-04 17:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-04 17:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-04 17:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-04 17:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-07 20:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-13 15:46   ` 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-110500-8800-dYVdeQAHpU@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox