IssueTracker

Component used: 'androidx.core:core-splashscreen:1.0.0' and 'androidx.drawerlayout:drawerlayout:1.1.1'

Devices/Android versions reproduced on:

• Emulator Android 9.0 Google Play
• Android-x86 9.0

The combination of a DrawerLayout with fitsSystemWindows=true and Splashscreen leads to a constant stream of messages on the MainLooper, which then will never become idle.

This has two effects:

• My espresso tests failed, because espresso waits for an idle message queue after launching an activity
• The app uses a huge amount of CPU (and therefore battery)

I attached a sample project. When it is run on Android 9.0 , the idle handler on the mainlooper (from MainActivity#onCreate) is never called, and you can see constant logcat messages like

2022-12-20 10:48:59.342  6772-6772  MessageQueue            de.iconparc.drawersplashscreentest   I  Message: >>>>> Dispatching to Handler (android.view.Choreographer$FrameHandler) {1ced8b7} android.view.Choreographer$FrameDisplayEventReceiver@fa43824: 0
2022-12-20 10:48:59.342  6772-6772  MessageQueue            de.iconparc.drawersplashscreentest   I  Message: <<<<< Finished to Handler (android.view.Choreographer$FrameHandler) {1ced8b7} android.view.Choreographer$FrameDisplayEventReceiver@fa43824
2022-12-20 10:48:59.357  6772-6772  MessageQueue            de.iconparc.drawersplashscreentest   I  Message: >>>>> Dispatching to Handler (android.view.Choreographer$FrameHandler) {1ced8b7} android.view.Choreographer$FrameDisplayEventReceiver@fa43824: 0
2022-12-20 10:48:59.358  6772-6772  MessageQueue            de.iconparc.drawersplashscreentest   I  Message: <<<<< Finished to Handler (android.view.Choreographer$FrameHandler) {1ced8b7} android.view.Choreographer$FrameDisplayEventReceiver@fa438242

When the same app is run on Android 11.0, everthings seems to work fine, and queueIdle: Queue is idle is printed to the logcat.

The issue seems to be connected to the window insets:

• DrawerLayout registers a OnApplyWindowInsetsListener
• The listener calls setChildInsets, which calls requestLayout()
• onMeasure of the DrawerLayout is called, which calls child.dispatchApplyWindowInsets on its children - providing an inset with a top inset > 0
• The children see a changed inset, and call requestApplyInsets
• dispatchApplyWindowInsets is called on the children with a top inset = 0
• the next requestlayout is handled and repeats the process

The children's' inset seems to change with each call between a top inset and no top inset.

I am not sure whether this is a bug in the DrawerLayout, but for some reason this only occurs when a SplashScreen is installed.