A bit ago toad went through all the code and added timeouts to all the the waits. His commit notes included:
apparently wait() can occasionally block forever on certain current JVMs. So always use the form with an argument. Don't use wait() anywhere, as the JVM has sadly been demonstrated to occasionally lose notifications - always use a timeout I just noticed someone went into QThreadFactory an took out the timeout. Was the timeout originally put there for a real JVM bug? The synchronization problem certainly needed to be fixed, but does the bug really exist? If so, we need to put that timeout back in. -Pascal _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
