Nothing is identified as a fix for this. But after a 'quick' test the issue looks like it may be fixed in the current trunk build. I'm still testing to see if the issue is triggered in other ways.