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 cryptic and seem to have been made prior to the kernel switch to git so I can't find any useful discussions about those comments and their implications. The common answer when people say "socket returns 0" is "you closed stdin" ... I wonder if fd 0 could have been closed on a different thread perhaps? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
