-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[bug] WebviewWindow freezes/loads infinite on creation inside js if tauri-plugin-devtools are inside Cargo.toml #10256
Comments
same it fixed it for me |
This is possibly one of the wildest bugs I have seen to date. Just declaring (not even using) causes a different crate to malfunction, just wild. Thanks for reporting! I have only today started investigating and I can already tell this is probably gonna be a longer process 😅 but it's promising a great writeup! Will keep this issue updated as I make progress on debugging this. Edit 1: I don't have a windows VM handy, but this appears to be affecting macOS only Edit 2: We have tracked down the issue. It is a pretty classic deadlock in the |
@thettler while we are working on a proper fix for this, here is a simple workaround: function openWindow() {
const pileWindow = new WebviewWindow('my-label', {
url: 'https://github.com/tauri-apps/tauri',
+ visible: false // initially hide the window
});
pileWindow.once('tauri:https://created', function () {
console.log('Success');
+ pileWindow.show(); // only show it after creation
});
pileWindow.once('tauri:https://error', function (e) {
console.log(e);
});
} |
Describe the bug
i try to create a new WebviewWindow from JS Code but every time it just loads infinite and i need to force quit the Program.
I figured out that it has something to do with the
tauri-plugin-devtools
. If i remove it from the Cargo.toml it works.Cargo.toml
main.rs
Reproduction
Repo
Expected behavior
No response
Full
tauri info
outputStack trace
No response
Additional context
https://discord.com/channels/616186924390023171/1260259980435521686
The text was updated successfully, but these errors were encountered: