It’s possible, thanks to your insight, that today’s 2.2.3.135 update at least partially addressed the issue you found. It might be instructive, because you may have a repeatable test case, for you to test again.