Comment 5 for bug 702057

@Timo: thanks for the report. This is a separate issue, unrelated to the issue described originally, and it is tracked by bug #763116, for which a fix has just been committed.

By the way, your analysis of the root cause of the issue was correct (congratulations!), although the fix is slightly more complex due to other considerations.