I have no idea why this happened or how to reproduce.
Perhaps related to bug#21602? In any case, here's a backtrace.