Skip to content

Conversation

grantland
Copy link
Contributor

setConnected uses the same lock we use for synchronizing disk I/O, so there's a possibility
that we can block the UI thread on disk I/O, so we're going to bump the lock usage to a
different thread.

Related Bug: https://developers.facebook.com/bugs/838833329491346/

@grantland grantland added type:bug Impaired feature or lacking behavior that is likely assumed needs review labels Aug 20, 2015
@grantland grantland added this to the 1.10.2 milestone Aug 20, 2015
@wangmengyan95
Copy link
Contributor

LGTM

`setConnected` uses the same lock we use for synchronizing disk I/O, so there's a possibility
that we can block the UI thread on disk I/O, so we're going to bump the lock usage to a
different thread.
grantland added a commit that referenced this pull request Sep 4, 2015
Don't share locks across UI thread and long running processes
@grantland grantland merged commit a2a1fd0 into master Sep 4, 2015
@grantland grantland deleted the grantland.ui_thread branch September 4, 2015 22:02
@facebook-github-bot
Copy link

@grantland updated the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants