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

[Regression] Segfault when running two instances #14

Closed
1 of 2 tasks
ModProg opened this issue May 5, 2021 · 1 comment · Fixed by #15
Closed
1 of 2 tasks

[Regression] Segfault when running two instances #14

ModProg opened this issue May 5, 2021 · 1 comment · Fixed by #15

Comments

@ModProg
Copy link

ModProg commented May 5, 2021

Describe the bug
Running wry twice it segfaults

Steps To Reproduce
cargo run --example hello_world & cargo run --example hello_world

Expected behavior
Two instances should start

LOG

(process:246998): Gtk-CRITICAL **: 09:57:30.630: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed

(process:246998): Gtk-CRITICAL **: 09:57:30.632: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed

(process:246998): Gtk-CRITICAL **: 09:57:30.632: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
Wry has started!
[1]  + 246998 segmentation fault (core dumped)  cargo run --example hello_world

Platform and Versions (please complete the following information):
OS: Linux
Rustc: 1.53.0-nightly (42816d61e 2021-04-24) also on stable

Would you assign yourself to resolve this bug?

  • Yes
  • No

Additional context
This is a regressing, 0.8.0 works fine

@wusyong
Copy link
Member

wusyong commented May 5, 2021

Thanks for the report!
Tested it and found this is caused by fixed application id introduced in v0.9
I'll make it None for now and maybe expose a method for users to set it.

@wusyong wusyong transferred this issue from tauri-apps/wry May 5, 2021
wusyong pushed a commit that referenced this issue May 5, 2021
fix: #14 remove fixed application id
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 a pull request may close this issue.

2 participants