android-strictmode-probe

To detect main thread violations, temporarily enable StrictMode in Application.onCreate to surface silent disk IO, network, and leak issues with penaltyLog, capturing stack traces in logcat without crashing the app.

StrictMode exposes performance issues by installing a temporary top-level thread policy in Application.onCreate that logs violations with stack traces pointing to your code when suspect flows are driven during startup and core interactions.

Yes, you can use StrictMode to find leaked objects by applying a temporary policy with penaltyLog only, which reports violations in logcat without triggering application crashes or altering runtime behavior.

The best way to clean up StrictMode is to use a dedicated cleanup gate to revert the temporary policy and remove the probe from Application.onCreate after driving fixes for the identified thread violations.

You need to enable StrictMode when diagnosing silent main thread performance issues during app startup or core interactions, specifically to reveal disk I/O, network operations, and leaked objects that degrade performance without crashing.

StrictMode logs stack traces instead of crashing because the temporary top-level policy is configured with penaltyLog only, capturing disk IO and network violation details in logcat to guide fixes while maintaining app stability.