Device free_memory isn't read at the time the event is captured

[bruno-garcia]

Description

Since free_memory is set on the scope when the SDK initializes, it doesn't accurately represent the free RAM at the time of the event.

It seems SentryCrash has the API that gives us this data. In which case it's likely it reads the data right before a crash. So possibly impact is just events captured at runtime (captureEvent, captureException, etc).

Data is put on scope here

sentry-cocoa/Sources/Sentry/SentryCrashIntegration.m

Lines 165 to 166 in b1ce7c5

	[SentrySDK.currentHub configureScope:^(SentryScope *_Nonnull outerScope) {
	[SentryCrashIntegration enrichScope:outerScope];

Related to #1104

[philipphofmann]

Instead of using an event processor, we could do this in prepare event

sentry-cocoa/Sources/Sentry/SentryClient.m

Line 418 in b1ce7c5

- (SentryEvent *_Nullable)prepareEvent:(SentryEvent *)event

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀