Hopefully the 28/06/19 Fix 1 version addresses this issue regardless; but knowing that is what causes it is really helpful - although I'll still have to look into it further to see why it's doing that, since I still can't find any evidence of the apparent affected variable being accessed by anything on that path.