getsentry / getsentry/sentry-java
Reevaluate usage of CopyOnWriteArrayList
Offen
Android
Improvement
- Vorherrschende Sprache
- Kotlin
- Sterne
- 1.4k
- Forks
- 478
- Ø Merge
- 2 T. 23 Std.
- Gemergte PRs (30 T.)
- 67
Beschreibung
### Description
This issue is a followup of https://github.com/getsentry/sentry-java/issues/2815
We use `CopyOnWriteArrayList` in several places. We should be careful, as that could cause OOM Errors (in specific cases).
We should find the hot paths which use it, and evaluate if it makes sense (performance wise) to replace it with an alternative approach.
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.