I'd say it's not fixed. The stacktrace from Bug #813454 looks pretty similar (more detailed though, might be worth sending it upstream), and the description says it occurred on 1.0.10.
I'd say it's not fixed. The stacktrace from Bug #813454 looks pretty similar (more detailed though, might be worth sending it upstream), and the description says it occurred on 1.0.10.