The evaluate is triggered in response to a binding, it's basically:
webview.Bind("rpc", func() {
go func() {
app.ui.eval("rpcResponse(42)")
}()
})
I wrote my own RPC wrapper on top of the one provided because some calls do network requests and thus need to be ran in a goroutine or it'd block the entire UI.
I've been able to reproduce this inconsistently on macOS (MBA, M2) and on Windows 10.
The chance of this segfault is like 0.1%, I have never been able to cause it on purpose, only during normal usage.
Please let me know if you need any further information, or know any launch options I could use to gather more information.
I am encountering a segfault very inconsistently and rarely right after calling Evaluate in a Dispatch callback.
I have following code that gets run from a separate goroutine from the main thread which called
webview.Run()
:Sometimes this segfaults in the main thread:
The evaluate is triggered in response to a binding, it's basically:
I wrote my own RPC wrapper on top of the one provided because some calls do network requests and thus need to be ran in a goroutine or it'd block the entire UI.
I've been able to reproduce this inconsistently on macOS (MBA, M2) and on Windows 10. The chance of this segfault is like 0.1%, I have never been able to cause it on purpose, only during normal usage.
Please let me know if you need any further information, or know any launch options I could use to gather more information.