I have been unable to reproduce the issue with the latest commit, so I would be inclined to believe the issue has been fixed.
Thanks for all your efforts. On Thu, Jun 01, 2017 at 11:40:29AM -0500, Matthew D. Fuller wrote: > I've managed to come up with a fix for the problem I can cause, which > I think is _probably_ the same one you're seeing. Fix is in trunk > now. > > Let me know if that does it for you; if not, we'll have to get more > creative to figure out what you're seeing. If it does fix it, I'll go > ahead and plan for a patch release shortly unless somebody finds new > regressions we need to stick into it.
