Hi @martijntje. You’re probably already aware, but just for context, this was closed due to the process I described in this post.
In this case, the bug was listed as having been fixed in 4.4.0, as you can see in the release notes. Looking at the internal bug report, I can see there were several changes made to fix this, including this PR.
Would you mind clarifying whether the bug — e.g. the situations it arrses — are identical to those you wrote about in your original bug report? I can create a new internal report about it, but any additional info you can provide would be really helpful, especially given this was tested internally and found to be fixed.