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 undefined behavior within load_tile_var_sizes #1748

Merged
merged 1 commit into from
Jul 28, 2020

Conversation

joe-maley
Copy link
Contributor

The load_tile_var_sizes is not thread-safe between TBB tasks because it
locks with an stdlib mutex. This change ensures that access to FragmentMetadata
instances are serialized.

The `load_tile_var_sizes` is not thread-safe between TBB tasks because it
locks with an stdlib mutex. This change ensures that access to FragmentMetadata
instances are serialized.
@joe-maley joe-maley force-pushed the jpm/fix-fragment-hang branch from d2d5de5 to 03f69e2 Compare July 28, 2020 18:58
@joe-maley joe-maley merged commit 1e4e48b into dev Jul 28, 2020
@joe-maley joe-maley deleted the jpm/fix-fragment-hang branch July 28, 2020 22:31
github-actions bot pushed a commit that referenced this pull request Jul 28, 2020
The `load_tile_var_sizes` is not thread-safe between TBB tasks because it
locks with an stdlib mutex. This change ensures that access to FragmentMetadata
instances are serialized.

Co-authored-by: Joe Maley <[email protected]>
Shelnutt2 pushed a commit that referenced this pull request Jul 29, 2020
The `load_tile_var_sizes` is not thread-safe between TBB tasks because it
locks with an stdlib mutex. This change ensures that access to FragmentMetadata
instances are serialized.

Co-authored-by: Joe Maley <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants