Has a bug been filed, ideally including the movie as an attachment, so that this issue doesn't get forgotten?
It's entirely possible that the issue manifests itself under some circumstances and not others (e.g. depending on the complexity of the object and the speed of the user's machine), but as bulia says, it's going to be difficult to fix until a developer manages to observe it live with a debugger up.
Filing the bug will help make sure that other developers get a crack at it.
I think we should focus on this for 0.45, but if it turns out to be very difficult to replicate and/or fix, probably what will happen is that we release 0.45 as-is, and address this along with any other missed bugs in a follow-up 0.45.1 release. That's often been the way we've had to do things in the past.
-mental