Comment 7 for bug 183419

Indeed it is. Thanks to the stacktrace, I can see where the pointer went null but have no idea how that code path could've been taken. It'd be kinda painful to check every foo->bar reference for nullness, or even what to do when that happens.

Maybe this should be forwarded upstream, since it's a development version and they'd be more interested about this crasher?

Judging from the stacktrace, it seems like you were toggling the fullsceen option which caused this.