Ya... there looks to be a timing related bug here. It has been addressed in a 2.5.2 beta (not yet released). We will discuss if it needs a maintenance release.
No good reason, you just found an error path that was neglected. This has also been corrected.