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
A user reported that calling sentry capture methods in fast succession is leading to issues, especially with screenshot integration.
Investigate if calling the SDK mehods in tight loops can be improved. One idea was to introduce a debounce for screenshots.
The minimal repro steps I got are attached, but this is a heavily contrived example aimed at easily reproducing the issue. In practice this would look like 30 API requests in short succession that all fail due to no internet connectivity or where all endpoints return an error code, where Sentry then creates exceptions in short succession.
The text was updated successfully, but these errors were encountered:
Description
A user reported that calling sentry capture methods in fast succession is leading to issues, especially with screenshot integration.
Investigate if calling the SDK mehods in tight loops can be improved. One idea was to introduce a debounce for screenshots.
The text was updated successfully, but these errors were encountered: