Comment 7 for bug 1460087

@Antonio

Agree 100% with need to handle this situation better. My motivation in the comment was to provide justification for moving this bug off 1.24. Solving the problem is likely to involve non-trivial engineering effort so would implementation during a development iteration, rather than during pre release stabilisation.

If we can reproduce this issue, I'd also like to gather information of the various deployment scenarios and also log files so we can diagnose the root cause etc.