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.


On 2012-02-04, Mihai Popescu <mihp...@gmail.com> wrote:
> I've run xxxterm from xterm on openbox this time, under some load
> stress pages (many big pictures slideshow style, waiting with patience
> for the pages to load).
> There it pops an error after each set of aprox. 100 pages:
>
> $ xxxterm
> xxxterm: config_parse: cannot open /home/uhmewrk/.xxxterm.conf: No
> such file or directory
>
> GLib-ERROR **: gmem.c:170: failed to allocate 8518 bytes
> Trace/BPT trap (core dumped)
>
> I've run xxxterm from gdb, and there is another message (sorry, I'm
> not a gdb expert):
>
> (gdb) file xxxterm
> Reading symbols from /usr/local/bin/xxxterm...(no debugging symbols
> found)...done.
> (gdb) run
> Starting program: /usr/local/bin/xxxterm
> xxxterm: config_parse: cannot open /home/uhmewrk/.xxxterm.conf: No
> such file or directory
> [New process 19921]
> [New process 19921, thread 0x855c4400]
> [New process 19921, thread 0x8a828c00]
>
> GLib-GIO-ERROR **: Creating pipes for GWakeup: Too many open files
>
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to process 19921, thread 0x7c89f800]
> 0x02e1930c in g_logv () from /usr/local/lib/libglib-2.0.so.2992.0
>
> I will move on to another snapshot, to see if those can be reproduced.

Reply via email to