We believe the issue is now fixed. The fix was merged as part of ticket 19430.

The fix is scheduled to be released with 4.4.0, 4.3.6 and 4.1-ESV-R15 releases.