Never mind, we've been able to reproduce it and an internal bug report has been created.