The problem I mentioned in comment #15 is now logged as bug 1833045. It's clearly different to this one.
The problem I mentioned in comment #15 is now logged as bug 1833045. It's clearly different to this one.