Interesting, that bug/patch was written by a guy I worked with at weta. He was always pushing code past its breaking point. I remember reading this bug before.
Looks like his fix didn’t have this bug.
It may have been modified later, his patch was from 2014.
