StrictMode
class StrictMode
kotlin.Any | |
↳ | android.os.StrictMode |
StrictMode is a developer tool which detects things you might be doing by accident and brings them to your attention so you can fix them.
StrictMode is most commonly used to catch accidental disk or network access on the application's main thread, where UI operations are received and animations take place. Keeping disk and network operations off the main thread makes for much smoother, more responsive applications. By keeping your application's main thread responsive, you also prevent ANR dialogs from being shown to users.
Note that even though an Android device's disk is often on flash memory, many devices run a filesystem on top of that memory with very limited concurrency. It's often the case that almost all disk accesses are fast, but may in individual cases be dramatically slower when certain I/O is happening in the background from other processes. If possible, it's best to assume that such things are not fast.
Example code to enable from early in your android.app.Application
, , or other application component's android.app.Application#onCreate
method:
override fun onCreate(savedInstanceState: Bundle?) { super.onCreate(savedInstanceState) StrictMode.setThreadPolicy( StrictMode.ThreadPolicy.Builder() .detectAll() .build() ) StrictMode.setVmPolicy( StrictMode.VmPolicy.Builder() .detectAll() .build() ) }
You can decide what should happen when a violation is detected. For example, using ThreadPolicy.Builder#penaltyLog
you can watch the output of adb logcat
while you use your application to see the violations as they happen.
If you find violations that you feel are problematic, there are a variety of tools to help solve them: threads, android.os.Handler
, android.os.AsyncTask
, , etc. But don't feel compelled to fix everything that StrictMode finds. In particular, many cases of disk access are often necessary during the normal activity lifecycle. Use StrictMode to find things you did by accident. Network requests on the UI thread are almost always a problem, though.
StrictMode is not a security mechanism and is not guaranteed to find all disk or network accesses. While it does propagate its state across process boundaries when doing calls, it's still ultimately a best effort mechanism. Notably, disk or network access from JNI calls won't necessarily trigger it.
Summary
Nested classes | |
---|---|
abstract |
When # |
abstract |
When # |
|
|
|
Public methods | |
---|---|
static StrictMode.ThreadPolicy! |
A convenience wrapper that takes the current |
static StrictMode.ThreadPolicy! |
A convenience wrapper that takes the current |
static Unit |
Enables the recommended StrictMode defaults, with violations just being logged. |
static StrictMode.ThreadPolicy! |
Returns the current thread's policy. |
static StrictMode.VmPolicy! |
Gets the current VM policy. |
static Unit |
noteSlowCall(name: String!) For code to note that it's slow. |
static Unit |
setThreadPolicy(policy: StrictMode.ThreadPolicy!) Sets the policy for what actions on the current thread should be detected, as well as the penalty if such actions occur. |
static Unit |
setVmPolicy(policy: StrictMode.VmPolicy!) Sets the policy for what actions in the VM process (on any thread) should be detected, as well as the penalty if such actions occur. |
Public methods
allowThreadDiskReads
static fun allowThreadDiskReads(): StrictMode.ThreadPolicy!
A convenience wrapper that takes the current ThreadPolicy
from getThreadPolicy
, modifies it to permit disk reads, and sets the new policy with setThreadPolicy
, returning the old policy so you can restore it at the end of a block.
Return | |
---|---|
StrictMode.ThreadPolicy! |
the old policy, to be passed to setThreadPolicy to restore the policy. |
allowThreadDiskWrites
static fun allowThreadDiskWrites(): StrictMode.ThreadPolicy!
A convenience wrapper that takes the current ThreadPolicy
from getThreadPolicy
, modifies it to permit both disk reads & writes, and sets the new policy with setThreadPolicy
, returning the old policy so you can restore it at the end of a block.
Return | |
---|---|
StrictMode.ThreadPolicy! |
the old policy, to be passed to setThreadPolicy to restore the policy at the end of a block |
enableDefaults
static fun enableDefaults(): Unit
Enables the recommended StrictMode defaults, with violations just being logged.
This catches disk and network access on the main thread, as well as leaked SQLite cursors and unclosed resources. This is simply a wrapper around setVmPolicy
and setThreadPolicy
.
getThreadPolicy
static fun getThreadPolicy(): StrictMode.ThreadPolicy!
Returns the current thread's policy.
getVmPolicy
static fun getVmPolicy(): StrictMode.VmPolicy!
Gets the current VM policy.
noteSlowCall
static fun noteSlowCall(name: String!): Unit
For code to note that it's slow. This is a no-op unless the current thread's has android.os.StrictMode.ThreadPolicy.Builder#detectCustomSlowCalls
enabled.
Parameters | |
---|---|
name |
String!: a short string for the exception stack trace that's built if when this fires. |
setThreadPolicy
static fun setThreadPolicy(policy: StrictMode.ThreadPolicy!): Unit
Sets the policy for what actions on the current thread should be detected, as well as the penalty if such actions occur.
Internally this sets a thread-local variable which is propagated across cross-process IPC calls, meaning you can catch violations when a system service or another process accesses the disk or network on your behalf.
Parameters | |
---|---|
policy |
StrictMode.ThreadPolicy!: the policy to put into place |
setVmPolicy
static fun setVmPolicy(policy: StrictMode.VmPolicy!): Unit
Sets the policy for what actions in the VM process (on any thread) should be detected, as well as the penalty if such actions occur.
Parameters | |
---|---|
policy |
StrictMode.VmPolicy!: the policy to put into place |