From: <dr...@bf...> - 2006-10-18 15:29:28
|
>> I use Chromium on Windows XP to drive 6 servers from one client over a >> 1Gbps TCP/IP network. Every now and then Chromium locks up. The lock up >> occurres in __tcpip_read_exact()'s call to recv(). Even though select() >> did report the socket to be ready for reading the first call to recv() >> blocks. If I kill the server of this connection recv() returns with the >> correct error code. See the stack trace below for more details. >> Does anyone else experience similar problems? I suspect this might be a >> bug in some network driver (Intel) but I'm not sure. > > If there's any bugs in Chromiums packer/unpacker code, a common > symptom is for the network layer to get stuck in recv() - waiting for > bytes that aren't coming. I dont think its a bug in Chromium since the block occurs on the first call to recv() after select() reported the socket to be readable. That is crTCPIPRecv() calls select(), finds the socket to be readable and calls crTCPIPReceiveMessage() which blocks right away on the statement if ( __tcpip_read_exact( sock, &len, sizeof(len)) <= 0 ). So this really shouldn't block or should it? > Is the lock-up only happening with certain apps? Do those apps work > ok on other Chromium systems? It does happen with at least a couple of apps I tried, one of which is atlantis. I didn't test on other systems though. Michael |