IMHO there's no point in re-opening this bug if no "extensive" help can be provided for debugging it. We tried to reproduce it but couldn't so far. So re-closing.