OSCrypt for gnome-keyring deadlocks on Init |
||
Issue descriptionScenario 1. OSCrypt is uninitialised (i.e. it will have to read its key from the keyring). It will be initialised lazily. 2. A client from thread T calls OSCrypt. OSCrypt acquires its thread-safety lock and schedules GetKeyDelegate() onto the main thread (because gnome-keyring requires to be called from the main thread) 3. A client from the main thread calls OSCrypt and waits on its thread-safety lock. 4. Deadlock: GetKeyDelegate is still scheduled on the main thread and is never executed. Affected users: systems which still haven't upgraded from gnome-keyring to libsecret. Frequency: unknown.
,
Mar 1 2018
This still happens
,
Nov 10
It still happens. It prevents chromium from starting when that happens. I can reproduce every time when I have two profile (not sure why), and when each of them have have save passwords (it is the decrypting of password_hash_data_list that seems to trigger the problem). |
||
►
Sign in to add a comment |
||
Comment 1 by sheriffbot@chromium.org
, Mar 1 2018