[runningcode]

📜 Description

This switches the DefaultCompositePerformanceCollector to use a monotonic clock for the collection deadline.
Before it seemed like it was using a monotonic clock but SentryNanotimeDate.nanoTimestamp return the epoch millis. 😢

Each CompositeData now holds a Deadline on options.getMonotonicTicker().

Tiny behavior changes:

• The 30 second boundary is now inclusive: Deadline.hasPassed() is >=, where the old check was >.
• addDataAndCheckTimeout no longer takes a shared nowNanos, since each transaction owns its own deadline.
• TestMonotonicTicker's field is now @Volatile, because the collector's timer thread reads a ticker the test thread advances.

💡 Motivation and Context

Clock-usage audit finding §C6.

• resolves: JAVA-579 (partially, the performance-collection budget only)
• part of: Remaining low-priority clock issues and clock-step regression coverage #5582

💚 How did you test it?

The two 30 second tests in DefaultCompositePerformanceCollectorTest now advance a TestMonotonicTicker instead of stubbing dateProvider.now() with a positional sequence of return values.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

The 100ms sampling loop in this class still runs on java.util.Timer, whose scheduling is wall-clock. Moving it is a scheduling change and gets its own PR.

🤖 Generated with Claude Code

[linear-code]

JAVA-579

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.63.0 (1)	release

⚙️ sentry-android Build Distribution Settings