-
Notifications
You must be signed in to change notification settings - Fork 281
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] tauri_plugin_log with TargetKind::Webview causes infinite log loop #2126
Comments
I can't reproduce this to be honest, do you have a minimal reproducible example I can test on? |
Thanks for taking a look! I'll try see if I can reproduce it in a new tauri app. |
I was able to reproduce in a completely new project, but only after adding a dependency for This is the full Cargo.toml
|
devtools and the log plugin are currently mutually exclusive because you can only have a single tracing subscriber, but this should actually result in a compilation error 🤔 ref https://docs.crabnebula.dev/devtools/troubleshoot/log-plugins/ |
ahh good to know thanks for the clarification! |
ah it's probably worth pointing out that I only had the
|
I'm not familiar with |
That's right. Although that alone doesn't trigger the problem which only arises when also adding the devtools plugin dependency. |
The error reported happens to be this line of code! |
@ayangweb well, I think this is another bug, probably you're logging uncaught errors and the log itself threw, I will open a fix for that right now |
@Legend-Master Overwrote and printed it to see if it helps you. |
Could you also log out |
I don't understand what you mean by that. |
Do you mind just copy the string in so I can see the full thing? I think the problems is probably |
|
Describe the bug
When using the
tauri_plugin_log
plugin with the Webview target as suchI get an infinite stream of
This is likely caused by the emit event handler emitting a lot which in turn calls the WebView target handler which calls emit etc..
I'm not sure if there's any config I'm supposed to have set to pre-filter that log message. Either one would need to avoid
emit
creating any log messages or try to manually not triggeremit
on such messages for WebView targets.Reproduction
No response
Expected behavior
No response
Full
tauri info
outputStack trace
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: