> Increase the limits in login.conf for the relevant login class;
> you'll need to logout and back in for them to take effect.
> You've hit both datasize and openfiles limits.
How much to increase them ? The login.conf is the one put by the
install. This error will fire even with one tab open in xxxterm. I
tested with 30 tabs open, 310MB memory for xxxterm displayed with top
and no crash. I rarely open 30 tabs at once.
In the meantime, X is not crashing anymore ( I have a new snapshot).
But I still got the error like this, even with only one tab open:
GLib-ERROR **: gmem.c:170: failed to allocate 8518 bytes
Trace/BPT trap (core dumped)
Running one tab of xxxterm with youtube I got this:
gram 'xxxterm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 532 error_code 162 request_code 149 minor_code 8)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
gram 'xxxterm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 575 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
(gdb) run --sync
Starting program: /usr/local/bin/xxxterm --sync
xxxterm: config_parse: cannot open /home/xxxuser/.xxxterm.conf: No
such file or directory
The program 'xxxterm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 575 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
[New process 20214, thread 0x88b02800]
