Just for my curiosity:
is there a function that translates major/minor in something readable ?
re,
wh
Am 30.03.2016 20:48, schrieb Ingo Bürk:
> Hi Lloyd,
>
> Adam already decoded the opcode for you. Just a quick Google search of
> request name + "BadAlloc" gives at least a few results. It might
Hi Lloyd,
Adam already decoded the opcode for you. Just a quick Google search of
request name + "BadAlloc" gives at least a few results. It might be
worth checking those out. I'm not familiar with GLX, unfortunately.
Regards
Ingo
On 03/30/2016 08:38 PM, Lloyd Brown wrote:
> Ingo,
>
> Thank you
Ingo,
Thank you for this.
Just for clarification, are we talking about system RAM or video card's RAM?
The reason I ask is this. Since we're an HPC lab, we do limit system
memory via memory cgroups, based on what the user's job requested. But
since seeing your email, I've gone as high as 64GB
Hi Lloyd,
see here: http://www.x.org/wiki/Development/Documentation/Protocol/OpCodes/
In your case you are trying to allocate way too much memory. This can
happen, for example, if you by accident try to create enormously large
pixmaps. Of course there's many things that can cause this. Decoding t
On Wed, 2016-03-30 at 10:03 -0600, Lloyd Brown wrote:
> Can anyone help me understand where the error messages, especially the
> major and minor opcodes, come from in an error like this one? Are these
> defined by Xorg, by the driver (Nvidia, in this case), or somewhere else
> entirely?
The major
Can anyone help me understand where the error messages, especially the
major and minor opcodes, come from in an error like this one? Are these
defined by Xorg, by the driver (Nvidia, in this case), or somewhere else
entirely?
> X Error of failed request: BadAlloc (insufficient resources for
> op
