Skip to content

runtime.errorString: runtime error: invalid memory address or nil pointer dereference #6525

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.

Sign up for GitHub

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

Jump to bottom
Open
status-sentry bot opened this issue Apr 14, 2025 · 3 comments · May be fixed by #6536
Open

runtime.errorString: runtime error: invalid memory address or nil pointer dereference #6525

status-sentry bot opened this issue Apr 14, 2025 · 3 comments · May be fixed by #6536
Assignees
@friofry
Labels
crash

Comments

@status-sentry
Copy link

status-sentry bot commented Apr 14, 2025

Sentry Issue: STATUS-GO-W

runtime.errorString: runtime error: invalid memory address or nil pointer dereference
  File "github.com/status-im/status-go/vendor/github.com/getsentry/sentry-go/stacktrace.go", line 28, in NewStacktrace
  File "github.com/status-im/status-go/vendor/github.com/getsentry/sentry-go/interfaces.go", line 393, in (*Event).SetException
  File "github.com/status-im/status-go/vendor/github.com/getsentry/sentry-go/client.go", line 547, in (*Client).EventFromException
  File "github.com/status-im/status-go/vendor/github.com/getsentry/sentry-go/client.go", line 492, in (*Client).RecoverWithContext
  File "github.com/status-im/status-go/vendor/github.com/getsentry/sentry-go/client.go", line 462, in (*Client).Recover
...
(13 additional frame(s) were not displayed)
@status-sentry status-sentry bot added the crash label Apr 14, 2025
@igor-sirotin
Copy link
Collaborator

@friofry I'm not sure if this one was resolved by #6489?

@friofry
Copy link
Contributor

friofry commented Apr 15, 2025

No this is different, I'll add a fix

friofry added a commit that referenced this issue Apr 16, 2025
@friofry
chore(rpc-client)_: fix test
947e8fc 
* method is not called, since the ctx is cancelled before the method is called

fixes #6525
@friofry friofry linked a pull request Apr 16, 2025 that will close this issue
Open
@friofry
Copy link
Contributor

friofry commented Apr 16, 2025 •
edited
Loading

It's an annoying problem that objects are used asynchronously after being deleted.
I believe it's not efficient to fix symptoms, so I've added a fix for the Rpc client, but it's probably not the only occurrence of this bug.

friofry added a commit that referenced this issue Apr 16, 2025
@friofry
chore(rpc-client)_: fix test
0fb7d9c 
* method is not called, since the ctx is cancelled before the method is called

fixes #6525
friofry added a commit that referenced this issue Apr 17, 2025
@friofry
chore(rpc-client)_: fix test
33d67f8 
* method is not called, since the ctx is cancelled before the method is called

fixes #6525
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@friofry friofry

Labels
crash
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix_: cancel ongoing requests when closing the ClientWithFallback status-im/status-go
2 participants
@friofry @igor-sirotin