Thanks for the report Eric, the bug is fixed in rev#74563.

This was a simple case to fix but given ES is becoming much more dynamic and as such, is it very useful to include a description of the events leading up to the crash. From the looks of things I would say this happened post-compilation or when adding/remove a class from the system, but it may not be that easy next time :)