From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102008] DRI_PRIME causes X Error of failed request: BadAlloc (insufficient resources for operation)
Date: Thu, 03 Aug 2017 03:26:14 +0000 [thread overview]
Message-ID: <bug-102008-502-1MgdcmnPXM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102008-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 888 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102008
--- Comment #4 from MWATTT <megwattt@gmail.com> ---
I also have this problem to with my laptop (Intel Skylake iGPU + AMD TOPAZ
dGPU)
The issue is only with opengl, radv works fine.
The BadAlloc only happens with some window sizes. It can be easily tested with
glxgears. For instance, there is no problem with 1600x900 or default size,
300x300. With this height (300), I can resize the width between 257 and 448
without hitting a BadAlloc.
With a width of 192, I have no problem with the following heights:
123, 124, 129, 123, 131, 132, 134, 135, 136, 139, 140, 145, 146, 147, 148, 150,
151, 152, 155, 156, 161
I have a BadAlloc with those heights:
125, 126, 127, 128, 133, 137, 138, 141, 142, 143, 144, 149, 153, 154, 157, 158,
159, 160
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1748 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 prev parent reply other threads:[~2017-08-03 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 21:20 [Bug 102008] DRI_PRIME causes X Error of failed request: BadAlloc (insufficient resources for operation) bugzilla-daemon
2017-08-02 1:42 ` bugzilla-daemon
2017-08-02 21:04 ` bugzilla-daemon
2017-08-03 0:25 ` bugzilla-daemon
2017-08-03 3:26 ` bugzilla-daemon [this message]
2017-08-04 13:52 ` 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-102008-502-1MgdcmnPXM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox