Bug 104351 - X Error of failed request: BadAlloc (insufficient resources for operation)
Summary: X Error of failed request: BadAlloc (insufficient resources for operation)
Status: RESOLVED DUPLICATE of bug 104306
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: 17.3
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-20 14:26 UTC by Breno Souza
Modified: 2017-12-28 20:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Breno Souza 2017-12-20 14:26:35 UTC
I was developing a Qt application using OpenGL. When I updated mesa to version 17.3.0-2, under Arch Linux, that application crashed and reported the X BadAlloc error.

First I suspected that this error was Qt related, so I ported my application to FreeGLUT. But then the same crash and error would emerge again.

I have downgraded mesa to version 17.2.6-1 and my application is functional again.

Just to be sure that was not related to my code, I ran glxinfo and glxgears under those versions and both commands worked as expected in version 17.2.6-1, but in version 17.3.0-2:

# glxgears
X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  149 ()
  Minor opcode of failed request:  2
  Serial number of failed request:  37
  Current serial number in output stream:  38

# glxinfo
name of display: :0
^C

I had to stop glxinfo, since there was no output after several minutes.

Thanks for your time,
Breno Souza
Comment 1 Emil Velikov 2017-12-20 15:51:04 UTC
Smells like something broken on your setup - be that miss-compiled Mesa or some local files are being picked up.

$ LD_DEBUG=libs glxinfo

Above will show you which binaries are picked up - it might be that you have some in /usr/local or elsewhere ;-)

We all `make install' sometimes and it leads to all sorts of fun. Thus I'd strongly recommend semi-regularly checking for 'disowned' files.

https://github.com/hakoerber/pacman-utils/blob/master/pacman-list-disowned-files
Comment 2 Breno Souza 2017-12-21 19:19:20 UTC
Same error on fresh install. I have installed the following packages:

base, base-devel, gnome, gnome-extra, freeglut, qt5-base, cower, pacaur, google-chrome (from aur), mesa-demos

I also have lost access to mesa 17.2.6-1 since I haven't saved it from my previously installation.

As of $ LD_DEBUG=libs glxinfo, binaries are located under /usr/lib. It halted on this line:

     10721:	calling init: /usr/lib/libnss_files.so.2
     10721:

I don't "make install" anything, maybe pacaur did. I don't know what to check in the disowned list.

I forget to mention that I use a Radeon HD 7850. Could it be something in my setup still? Is this distro related?

Thanks for your time,
Breno Souza
Comment 3 Emil Velikov 2017-12-22 14:43:09 UTC
(In reply to Breno Souza from comment #2)
> Same error on fresh install. I have installed the following packages:
> 
> base, base-devel, gnome, gnome-extra, freeglut, qt5-base, cower, pacaur,
> google-chrome (from aur), mesa-demos
> 
> I also have lost access to mesa 17.2.6-1 since I haven't saved it from my
> previously installation.
> 
You might have overdone it a bit (aka fresh install isn't necessary), but at least we know it's a nice clean setup.

Regarding old binaries/packages see the wiki
https://wiki.archlinux.org/index.php/Arch_Linux_Archive

> As of $ LD_DEBUG=libs glxinfo, binaries are located under /usr/lib. It
> halted on this line:
> 
>      10721:	calling init: /usr/lib/libnss_files.so.2
>      10721:
> 
> I don't "make install" anything, maybe pacaur did. I don't know what to
> check in the disowned list.
> 
I'd recommend slowing learning the tools you use (pacaur). Normally you'll be looking for libraries (*.so*), but that's not applicable now since you've got a clean setup.

> I forget to mention that I use a Radeon HD 7850. Could it be something in my
> setup still? Is this distro related?
> 
Knowing the hardware is a important detail - it sounds similar (sort of) to bug 104306.

Most likely you're using a Wayland session - try a Xorg one (there should be some toggles on the login screen).
Comment 4 Breno Souza 2017-12-26 13:43:22 UTC
It worked, thanks! I can't get why tough. Should I report this bug on Wayland instead?

I'm kind of a newbie in this report bug things, should I change the status of this one?

Thanks for your time,
Breno Souza
Comment 5 Emil Velikov 2017-12-28 20:28:30 UTC
Let's mark this as duplicate for now.
If the solution of bug 104306 does not help feel free to reopen.

In the interim use the Xorg workaround and keep a close eye on bug 104306.

*** This bug has been marked as a duplicate of bug 104306 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.