You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can lead to a deadlock. If at the end of the "if" scope mir_buffer is the last remaining owner of the buffer, then the destructor will be called. The destructor also tries to lock the mutex: crunch!
The text was updated successfully, but these errors were encountered:
356: Don't hold a lock while potentially destroying an object that uses it. r=wmww a=AlanGriffiths
Don't hold a lock while potentially destroying an object that uses it. (Fixes#355)
Co-authored-by: Alan Griffiths <alan@octopull.co.uk>
borsbot
added a commit
that referenced
this issue
May 9, 2018
356: Don't hold a lock while potentially destroying an object that uses it. r=wmww a=AlanGriffiths
Don't hold a lock while potentially destroying an object that uses it. (Fixes#355)
Co-authored-by: Alan Griffiths <alan@octopull.co.uk>
356: Don't hold a lock while potentially destroying an object that uses it. r=wmww a=AlanGriffiths
Don't hold a lock while potentially destroying an object that uses it. (Fixes#355)
Co-authored-by: Alan Griffiths <alan@octopull.co.uk>
This can lead to a deadlock. If at the end of the "if" scope
mir_buffer
is the last remaining owner of the buffer, then the destructor will be called. The destructor also tries to lock the mutex: crunch!The text was updated successfully, but these errors were encountered: