New issue
Advanced search Search tips

Issue 697478 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

OSCrypt for gnome-keyring deadlocks on Init

Project Member Reported by cfroussios@chromium.org, Mar 1 2017

Issue description

Scenario
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.




 
Project Member

Comment 1 by sheriffbot@chromium.org, Mar 1 2018

Status: Archived (was: Available)
This issue has been available for more than 365 days with no owner or cc list, so archiving this bug. Please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Internals>LocalDataEncryption
Status: Available (was: Archived)
This still happens 
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