Closed Saviq closed 5 years ago
It turns out this is a thread-synchronization problem: one thread is still processing the launch after another deleted the instance. In here it was after ctrl+c
, but it could have been parallel clients.
The agreement to address this is to use QReadWriteLock
to lock obviously destructive operations in the delete procedure, locking it only for reading in other operations, for the time being.
Backtrace: