Comment #12 on issue 27446 by codedr: socket() sometimes returns zero
despite stdin still being open
http://code.google.com/p/chromium/issues/detail?id=27446
I'm not seeing this error in recent tests.
Thanks.
--
You received this message because you are listed in the owner
or CC fields of th
Updates:
Labels: Mstone-X
Comment #11 on issue 27446 by e...@chromium.org: socket() sometimes returns
zero despite stdin still being open
http://code.google.com/p/chromium/issues/detail?id=27446
agl says that fd exhaustion would produce -1 instead of 0.
--
You received this message b
Comment #10 on issue 27446 by codedr: socket() sometimes returns zero
despite stdin still being open
http://code.google.com/p/chromium/issues/detail?id=27446
I've pulled the latest changesets and have run into a build problem.
I'm working on the issue and will report the results of my tests.
-
Comment #9 on issue 27446 by craig.schlenter: socket() sometimes returns
zero despite stdin still being open
http://code.google.com/p/chromium/issues/detail?id=27446
I have been running for several days with some debugging code and I haven't
seen any
instances of socket returning 0.
codedr:
Comment #8 on issue 27446 by craig.schlenter: socket() sometimes returns
zero despite stdin still being open
http://code.google.com/p/chromium/issues/detail?id=27446
I'm not sure what the problem is :( ... I would expect fd exhaustion to
return ENFILE
though. The kernel comments are somewhat
Comment #7 on issue 27446 by e...@chromium.org: socket() sometimes returns
zero despite stdin still being open
http://code.google.com/p/chromium/issues/detail?id=27446
Craig's comment suggests fd exhaustion. Perhaps you can poke around with
lsof or
/proc/pid/fd to see if htat's happening.
-
Comment #5 on issue 27446 by codedr: socket() sometimes returns zero
despite stdin still being open
http://code.google.com/p/chromium/issues/detail?id=27446
i'm currently running:
Linux rodan 2.6.27.21-0.2-default #3 SMP PREEMPT Thu Nov 5 10:26:08 CST
2009 x86_64
x86_64 x86_64 GNU/Linux
It's
Comment #4 on issue 27446 by craig.schlenter: socket() sometimes returns
zero despite stdin still being open
http://code.google.com/p/chromium/issues/detail?id=27446
So there is a nice introduction to where all the socket stuff lives in the
kernel
here: http://www.skyfree.org/linux/kernel_net
