-
-
Notifications
You must be signed in to change notification settings - Fork 441
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
Initialize SentryOptions members lazily #2541
Labels
Milestone
Comments
github-project-automation
bot
moved this to Needs Discussion
in Mobile & Cross Platform SDK
Feb 14, 2023
We could even lazily initialize elements of SentryOptions on |
7 tasks
7 tasks
github-project-automation
bot
moved this from Todo
to Done
in Mobile & Cross Platform SDK
Oct 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When SentryOptions.empty() is used (e.g. in a
NoOpHub
), we still eagerly initialize some of the class members, for example:I think, those should be fine to initialize lazily, so in case of the empty options they do not cause potential issues. There was a recent customer report of an ANR caused by with Sentry frames in it (although the ANR is most likely not caused by Sentry, because there's nothing involved that should cause an ANR, but still we'd like to eliminate such issues):
The text was updated successfully, but these errors were encountered: