This issue is now fully resolved in version 4.5.9. Work on version 4.6.1 has started which will include this fix.