From: Brian P. <bri...@tu...> - 2006-10-18 14:37:27
|
Michael D=FCrig wrote: > Hi >=20 > I use Chromium on Windows XP to drive 6 servers from one client over a=20 > 1Gbps TCP/IP network. Every now and then Chromium locks up. The lock up= =20 > occurres in __tcpip_read_exact()'s call to recv(). Even though select()= =20 > did report the socket to be ready for reading the first call to recv()=20 > blocks. If I kill the server of this connection recv() returns with th= e=20 > correct error code. See the stack trace below for more details. > Does anyone else experience similar problems? I suspect this might be a= =20 > bug in some network driver (Intel) but I'm not sure. If there's any bugs in Chromiums packer/unpacker code, a common=20 symptom is for the network layer to get stuck in recv() - waiting for=20 bytes that aren't coming. Is the lock-up only happening with certain apps? Do those apps work=20 ok on other Chromium systems? -Brian |