On 04 Sep 2011, at 22:35, Sven Van Caekenberghe wrote: > OK, thanks for the extra info. > I'll see what I can do tomorrow, after thinking about this a bit. > If I can't reproduce this, I can't debug it.
I am really very confused and don't understand what is happening, but here is what I found out: Starting from the partial build artifact seaside3.[image|changes] #720 from http://jenkins.lukas-renggli.ch and using the VM http://www.mirandabanda.org/files/Cog/VM/VM.r2370/ on my Ubuntu 11.04 I finally could replicate a problem loading builder/scripts/seaside3-zinc.st. Now the hang (100% cpu, no crash or any log to be seen) only happens in two cases: running from the command line (as in the build script): ./coglinux/bin/squeak -nodisplay -nosound seaside3.image /home/sven/Smalltalk/builder/scripts/seaside3-zinc.st or doing a file in of this file using the File Browser in Pharo. Executing the same code manually (selecting it and performing a doit) works fine. Note to replicate this you have to use a specific version, as in Gofer new squeaksource: 'ZincHTTPComponents'; version: 'Zinc-HTTP-SvenVanCaekenberghe.191'; package: 'Zinc-Seaside'; load. And then starting the Seaside adapter in one go. On Mac OS X, I cannot reproduce this at all. The difference between the working version (188) and the failing ones (up until 191) is very small IMHO, that's what is so strange. So I decided to revert back by pushing down the connection management functionality of ZnMultiThreadedServer to a new subclass called ZnManagingMultiThreadedServer. Now the code difference between working and failing code is even smaller. Note also that the server is just started, it is not yet receiving any connections! Any help would be appreciated ;-) Lukas, I think you could try to rebuild the failing Seaside jobs. Sven
