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.

Sign up for GitHub

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

Jump to bottom

The return value of Win32 API GetCurrentThread is only valid in the calling thread, not unique in process scope. #77

Closed
JX-Master opened this issue Sep 21, 2024 · 0 comments · Fixed by #79
Closed

The return value of Win32 API GetCurrentThread is only valid in the calling thread, not unique in process scope. #77

JX-Master opened this issue Sep 21, 2024 · 0 comments · Fixed by #79
Assignees
@JX-Master
Labels
bug Something isn't working
Milestone
v0.9

Comments

@JX-Master
Copy link
Owner

No description provided.

@JX-Master JX-Master added the bug Something isn't working label Sep 21, 2024
@JX-Master JX-Master added this to the v0.9 milestone Sep 21, 2024
@JX-Master JX-Master self-assigned this Sep 21, 2024
@JX-Master JX-Master linked a pull request Sep 22, 2024 that will close this issue
[Runtime]Fix incorrect use of ::GetCurrentThread to get thread handle on Windows. #79
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JX-Master JX-Master

Labels
bug Something isn't working
Projects
None yet
Milestone
v0.9
Development

Successfully merging a pull request may close this issue.

[Runtime]Fix incorrect use of ::GetCurrentThread to get thread handle on Windows. JX-Master/LunaSDK
1 participant
@JX-Master