Hi,
============ the original question ============
We are running Tru64 5.0A on an XP1000 (and using CDE and a PowerStorm 350
board if that's important). Under conditions of heavy usage (lots of
processes running due to two invocations of our large image processing
app), a third invocation of our app quits with this message:
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 1 (X_CreateWindow)
Serial number of failed request: 166776
Current serial number in output stream: 166782
At first I wasn't convinced that the problem was specifically related to X
Windows: thinking that we were running out of processes, I increased
max_proc_per_user from 256 to 1024 -- but no change (that is, still get the
above error message). Then I ran a script that created hundreds of small
processes having no graphics/GUIs/etc.; this didn't seem to cause any
problems. Using this same script to start 100+ invocations of xclock DID
cause some problems with the window manager but no error messages that I'm
aware of. This makes me think that it IS X-related in some way. Can
someone shed some light on this? Are there some sysconfig or X parameters
that I can tweek?
======================
My thanks to these two respondents...
"Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com>...
>I believe that there IS an upper limit on the number of open windows
>that the Tru64 UNIX X server can support; I remember discussions in
>some of the release meetings along the way about this. I have no idea
>how many windows your application creates, but with CDE (which itself
>probably uses a fair amount of X resources, including reserving the
>data structures associated with "windows"), it's altogether possible
>that you've simply run the X server out of resources. After all, you
>are getting an "insufficient resources for operation" error out of the
>X libraries in reaction to an "X_CreateWindow" operation; this comes
>from the X server back to the library and thence to the application.
>
>I am confident that there is no sysconfig parameter that is likely to
>affect this. Unless you see something in the Xdec reference page to
>indicate otherwise, I doubt it's tunable in the X server either; I'd
>bet it's a compiled in limit (but I'd have to go wading through the
>X server sources to confirm this, and trust me, I don't want to have
>to try to do that).
It looks like X has nothing in its command line options that would help;
Xdec might, but it's hard to tell.
"John J. Francini" <francini_at_zk3.dec.com>...
>I'm wondering if the X server or your app
>is running afoul of one of these proc parameters:
>
> max_per_proc_address_space
> max_per_proc_data_size
> max_per_prox_stack_size
>
>If you increase the value of any of these parameters, you will need
>to reboot to see what effect it has on your application's behavior.
I increased max_per_proc_stack_size & max_per_proc_data_size (and
rebooted), but this had no effect on the problem, but it was a good try
anyway...
Thanks again,
Peyton
University of Michigan, Radiology
voice: 734-647-0849
FAX: 734-764-8541
e-mail: bland_at_umich.edu
URL:
http://www.med.umich.edu/dipl/
Received on Thu Dec 14 2000 - 21:03:06 NZDT