Fix ABI mismatch in INIT_MAIN_THREAD_ID for Windows runtime #4442
+5
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kchibisov
approved these changes
Dec 16, 2025
Legend-Master
added a commit
to tauri-apps/tao
that referenced
this pull request
Dec 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
changelogmodule if knowledge of this change could be valuable to usersThis PR fixes Issue Windows: INIT_MAIN_THREAD_ID uses wrong ABI #4435 by correcting the ABI used in the Windows global constructor INIT_MAIN_THREAD_ID. The function was previously declared with the Rust ABI (fn()), which is not guaranteed to match the Windows runtime expectations. It has now been updated to use the proper C ABI (extern "C" fn()), ensuring stable and correct behavior when the runtime invokes the constructor.