|
|
On Sun, 06 Jul 2008 16:30:51 -0000, 0 <root@xxxxxxxxxxxxxxxx> wrote:
> Okay, so 9.51 came out. I downloaded it and installed
> it, and it now consumes one-hundred percent of my cpu.
>
> My ~/.xsession-errors file has thousands of lines like
> this:
>
> Failed to connect. Check ulimit value: Too many open files
> Failed to open file. Check ulimit value: Too many open files
>
> No, I don't have any limits:
>
> $ ulimit
> unlimited
Are you sure?
grahn@tuva:~$ ulimit
unlimited
grahn@tuva:~$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
max nice (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) unlimited
max rt priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
I cannot see from a quick glance in the documentation which limit a
plain 'ulimit' shows, but it sure isn't the open files limit, or the
core file size, or ...
> lsof shows opera with 2048 open files (including the ones
> used by operapluginwrapper).
Each process has its own limit, but yes, that must surely be the limit
you hit. And yes, it seems like a bug. Include the lsof output in
the bug report, so they can see which files (or sockets, etc) are
involved.
/Jorgen
--
// Jorgen Grahn <grahn@ Ph'nglui mglw'nafh Cthulhu
\X/ snipabacken.se> R'lyeh wgah'nagl fhtagn!
|
|