Thanks for the new discovery! This is potentially fixed in 6.0b but I'm leaving this thread open for now... this is a complicated area of code and this issue would only happen occasionally to begin with, so it's hard to be sure whether it's completely fixed.