Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix deadlock when canceling processor task #374

Merged
merged 2 commits into from
Jun 15, 2017

Conversation

zachwaugh
Copy link
Contributor

Use direct ivar access for _downloadTaskUUID since self.downloadTaskUUID uses a lock as well and causes a deadlock when called here. Fixes #372

Copy link
Collaborator

@maicki maicki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @zachwaugh for working on that - Looks good to me.

@garrettmoon Curious if in this place we should use locked_downloadTaskUUID instead of using the instance variable directly.

@garrettmoon
Copy link
Collaborator

@zachwaugh Thank you so much for the investigation and fix here!

@maicki my opinion is it's not necessary here since it would essentially just be a method that purely wrapped the ivar?

@garrettmoon
Copy link
Collaborator

garrettmoon commented Jun 15, 2017

@zachwaugh Mind adding an entry to CHANGELOG.md?

@zachwaugh
Copy link
Contributor Author

@garrettmoon sure thing, just updated it

Copy link
Collaborator

@maicki maicki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@garrettmoon Makes sense, so let's get that in!

@garrettmoon garrettmoon merged commit 7415e31 into pinterest:master Jun 15, 2017
garrettmoon pushed a commit that referenced this pull request Jun 15, 2017
* Use direct ivar access to fix deadlock on accessing downloadTaskUUID

* Add changelog entry
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants