-
Notifications
You must be signed in to change notification settings - Fork 28
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
Crash in HTTPMetrics : Attempted to dereference garbage pointer #59
Comments
Metrics may fire after |
@malcommac thanks for your feedback! Unfortunately I can't reproduce it.. The trace is from Sentry and it has been triggered somehow by one of our users.. I couldn't reproduce or trigger any crash during development and testing... but nothing beats real-usage made by daily users apparently... |
I'm inviting you to try 1.7 when it will be out. I'll check in our products too but I'm confident it's gone with the latest changes. Thank you again for your feedback! |
Thanks @malcommac I'll upgrade to 1.7 as soon as it's available and will report back if the problem still arises |
@malcommac do you have an ETA for the 1.7 release? Should I switch to the |
Hi! We'll release 1.7 the upcoming week. After the release we also plan to move the HTTPStubber as separate package too. |
released |
Bug Report
Summary
It seems that there is still something going on with HTTPMetrics in the 1.5.2 version.
I can't reproduce it since I don't really know what's going on, but our crash report shows a considerable amount of these issues...
FYI, we use the Sentry and NewRelic SDKs and I am not sure if they could interfere with RealHTTP somehow 🤔
The text was updated successfully, but these errors were encountered: