lp:1707931 triggered the same assertion as this issue, but has a WIN32 specific initiating event. So this can not be the same issue that Klemen saw. However, the additional locking may fix this as well.
lp:1707931 triggered the same assertion as this issue, but has a WIN32 specific initiating event. So this can not be the same issue that Klemen saw. However, the additional locking may fix this as well.