You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have no idea how to reproduce this, I've been getting this for months randomly and I can't narrow it down or reproduce consistently.
We use webview.Dispatch to evaluate code that sends RPC responses to JS land (we built our own RPC ontop of webview RPC because we needed async procedures).
This works without issues 99.999% of time, until it doesn't and crashes.
According to our observations, this might be related to navigations? We do "reloadless" navigations in our SPA and crashes seem to happen frequently imminently before/after one.
panic: runtime error: invalidmemoryaddressornilpointerdereference
[signal0xc0000005code=0x0addr=0x0pc=0x7ff62432dbcd]
goroutine1 [running, lockedtothread]:
github.com/webview/webview_go._webviewDispatchGoCallback(0xc8)
C:/Users/runneradmin/go/pkg/mod/github.com/webview/webview_go@v0.0.0-20230901181450-5a14030a9070/webview.go:217+0xadgithub.com/webview/webview_go._Cfunc_webview_run(0x15d0933d130)
_cgo_gotypes.go:238+0x49github.com/webview/webview_go.(*webview).Run.func1(0xc00009fcb8?)
C:/Users/runneradmin/go/pkg/mod/github.com/webview/webview_go@v0.0.0-20230901181450-5a14030a9070/webview.go:157+0x34github.com/webview/webview_go.(*webview).Run(0xc00007e630?)
C:/Users/runneradmin/go/pkg/mod/github.com/webview/webview_go@v0.0.0-20230901181450-5a14030a9070/webview.go:157+0x13// .... our code that just calls Run
Getting a nil pointer deref here:
webview_go/webview.go
Line 217 in 5a14030
I have no idea how to reproduce this, I've been getting this for months randomly and I can't narrow it down or reproduce consistently.
We use
webview.Dispatchto evaluate code that sends RPC responses to JS land (we built our own RPC ontop of webview RPC because we needed async procedures).This works without issues 99.999% of time, until it doesn't and crashes.
According to our observations, this might be related to navigations? We do "reloadless" navigations in our SPA and crashes seem to happen frequently imminently before/after one.