Skip to content

Conversation

@tobil4sk
Copy link
Member

When threads are enabled, it's possible that other threads are still running while neko is shutting down. This means freeing builtins or the thread local storage slot for the vm context may cause a crash on those threads.

Closes #281.

@tobil4sk tobil4sk force-pushed the fix/threads-crash-global-free branch from 256f845 to 7d10f27 Compare February 15, 2025 13:29
When threads are enabled, it's possible that other threads are still
running while neko is shutting down. This means freeing builtins or the
thread local storage slot for the vm context may cause a crash on those
threads.
@Simn
Copy link
Member

Simn commented Apr 14, 2025

Should I merge this? I thought there were potential problems here, but maybe I'm confusing this with #305.

@tobil4sk
Copy link
Member Author

You mentioned a concern about whether it's correct to not free any globals at all here, but it was #305 (not this one) with issues for the haxelib server.

@Simn Simn merged commit 905c179 into HaxeFoundation:master Apr 14, 2025
16 checks passed
@tobil4sk tobil4sk deleted the fix/threads-crash-global-free branch April 14, 2025 17:13
@kLabz
Copy link

kLabz commented Apr 15, 2025

So could we get a neko release? That would allow me to release Haxe 4.3.7

@Simn
Copy link
Member

Simn commented Apr 15, 2025

Who is able to do that?

@kLabz
Copy link

kLabz commented Apr 15, 2025

@tobil4sk
Copy link
Member Author

2.4.1 has been released with this fix: https://github.com/HaxeFoundation/neko/releases/tag/v2-4-1, and I've opened a PR for haxe to use this new version

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.

Neko thread usage causes seg faults during global free

3 participants