Hi Chris,
<br>
Sorry for not getting back to you. Yes, I believe this issue has been fixed in 2.4. We didn't file a bugreport for it, so it didn't appear in the changelog. Feel free to test using the Portable build, if you don't want to update the installed version before having tested.
Please let us know if you can trigger it again.