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

Avoid dangling lambda-script links when former destroyed earlier #85223

Closed

Conversation

RandomShaper
Copy link
Member

Additionally, mutex usage is made more correct.

Fixes #85151.

Tested the following recent related bugs are still gone after this PR (plus no address sanitizer issues detected);

Again, given how convoluted all this is, serious testing is welcome with real-world projects, hot reloading, etc., etc.

@RandomShaper RandomShaper added this to the 4.2 milestone Nov 22, 2023
@RandomShaper RandomShaper requested a review from a team as a code owner November 22, 2023 15:35
@akien-mga
Copy link
Member

Additionally, mutex usage is made more correct.
@adamscott
Copy link
Member

TSAN still complains. 😬 😓

@RandomShaper
Copy link
Member Author

Superseded by #85248.

@YuriSizov YuriSizov removed this from the 4.2 milestone Nov 22, 2023
@RandomShaper RandomShaper deleted the fix_gdlamb_doublefree branch February 21, 2024 09:03
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.

GDScript engine destruction causes deadlock when destroying lambdas
6 participants