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

set_t while free_cell callbacks are running #3500

Closed
wants to merge 1 commit into from

Conversation

vladpaiu
Copy link
Member

Summary
Potential fix for #3498

Details
Potential fix for #3498

Solution
set_t while free_cell callbacks are running

Compatibility
Should be compatible

Closing issues

Copy link

Any updates here? No progress has been made in the last 30 days, marking as stale.

@github-actions github-actions bot added the stale label Nov 17, 2024
@github-actions github-actions bot closed this Nov 24, 2024
@vladpaiu vladpaiu reopened this Nov 24, 2024
@github-actions github-actions bot closed this Dec 2, 2024
@vladpaiu vladpaiu reopened this Dec 2, 2024
@stale stale bot removed the stale label Dec 2, 2024
Copy link

Any updates here? No progress has been made in the last 30 days, marking as stale.

@github-actions github-actions bot added the stale label Jan 21, 2025
@github-actions github-actions bot closed this Jan 29, 2025
@vladpaiu vladpaiu reopened this Jan 29, 2025
@stale stale bot removed the stale label Jan 29, 2025
Copy link

github-actions bot commented Mar 1, 2025

Any updates here? No progress has been made in the last 30 days, marking as stale.

@github-actions github-actions bot added the stale label Mar 1, 2025
@bogdan-iancu bogdan-iancu self-assigned this Mar 5, 2025
@stale stale bot removed the stale label Mar 5, 2025
@bogdan-iancu
Copy link
Member

@vladpaiu , thanks for the work here. IMHO, in regards to the #3498 issue, the fix should not be setting a new T while running the destroy callbacks (there is no need for the value), but rather to be sure the T is cleaned up at the end of any previous processing. Some TM code is "leaking" the T value.... and fixing this leaking should be the proper approach.

@bogdan-iancu
Copy link
Member

The #3498 crash is more likely to be fixed by #3502 . The change here is not fixing anything IMHO, so let's skip it.

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.

2 participants