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.

Sign up for GitHub

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

Jump to bottom

In p2p code, iterator is not robust to concurrent modification in _handle_message_calls_in_progress loop #182

Open
vikramrajkumar opened this issue Jan 18, 2017 · 0 comments
Open

In p2p code, iterator is not robust to concurrent modification in _handle_message_calls_in_progress loop #182

vikramrajkumar opened this issue Jan 18, 2017 · 0 comments
Labels
3d Bug Classification indicating the existing implementation does not match the intention of the design
Milestone
Future Feature Re...

Comments

@vikramrajkumar
Copy link
Contributor

From @theoreticalbts on February 25, 2016 16:3

The problem is here. The code walks an std::list using an iterator, but the cancel_and_wait() call allows other FC tasks to run, some of which modify the list and invalidate the iterator.

Copied from original issue: cryptonomex/graphene#598
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3d Bug Classification indicating the existing implementation does not match the intention of the design
Projects
None yet
Milestone
Future Feature Release
Development

No branches or pull requests
2 participants
@vikramrajkumar @abitmore