Skip to content

Fix concurrency bug related to resource monitors #1603

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

Merged

Conversation

pguyot
Copy link
Collaborator

@pguyot pguyot commented Mar 29, 2025

Use ref count and lock on list of monitors for a resource type to ensure that resource still exists when calling the monitor handler.

Should fix #1589

These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).

SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

Use ref count and lock on list of monitors for a resource type to ensure that
resource still exists when calling the monitor handler.

Signed-off-by: Paul Guyot <[email protected]>
@bettio bettio merged commit d416d90 into atomvm:release-0.6 Mar 29, 2025
135 of 140 checks passed
@pguyot pguyot deleted the w13/fix-resource-monitor-concurrency-issue branch March 29, 2025 09:57
bettio added a commit that referenced this pull request Mar 29, 2025
Merge fixe for resources concurrency bug (#1603) and fixes for memory
corruptions (#1600 and #1601) from release-0.6 branch.
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.

2 participants