Comment 150 for bug 1308105

I'm really impressed, thanks to the persistence with trying to find a solution to this bug. As several of you have mentioned, the patch in #53 / #54 (courtesy of jkampe68) seems to resolve the issue. I have tested this patch myself, and while not being able to reproduce the original issue, I have verified that there do not seem to be any regressions with this patch.

I have committed this change here:

I'm planning to do a new release including this patch shortly. HUGE shout out to everyone that helped figure this one out!