Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 80bd0e87 authored by Andre Le's avatar Andre Le
Browse files

Using background scope instead of application scope in DesktopInteractor 

Using application scope in this interactor is likely to cause the lock
contention described in the bug. We need to use background scope
instead.

Bug: 433198838
Flag: NEXEMPT fix perf test
Test: DesktopInteractorTest
Change-Id: I9813280915b78e607598f7303012e6eea38837be
parent 859c6c2c

packages/SystemUI/src/com/android/systemui/desktop/domain/interactor/DesktopInteractor.kt

+2 −2
Original line number Diff line number Diff line
@@ -18,7 +18,7 @@ package com.android.systemui.desktop.domain.interactor 


import android.content.res.Resources

import com.android.systemui.dagger.SysUISingleton

import com.android.systemui.dagger.qualifiers.Application

import com.android.systemui.dagger.qualifiers.Background

import com.android.systemui.dagger.qualifiers.Main

import com.android.systemui.res.R

import com.android.systemui.statusbar.policy.ConfigurationController
@@ -36,7 +36,7 @@ class DesktopInteractor 
@Inject

constructor(

    @Main private val resources: Resources,

    @Application private val scope: CoroutineScope,

    @Background private val scope: CoroutineScope,

    configurationController: ConfigurationController,

) {