It is very unlikely you will be able to reproduce it: it was the result of a geometry update on an object that vanished due to a race condition of some kind; such cases happen, but are normally properly caught in the code by NULL and dead objects checks.
I added one more such (apparently redundant, but perhaps not after all) check for next release.