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

Commit 2ea6d96b authored by Chavi Weingarten's avatar Chavi Weingarten
Browse files

Add timeout log if sync transaction is not applied 

There are a few cases where the sync transaction is sent to WMS which
means it becomes outside the SSG control. In most cases, there's already
a timeout for BlastSyncEngine when sending the transaction back to
shell, but there are some exceptions.

This log will help identify if there are cases where something is
requesting to sync the buffer but isn't applying it.

Test: Builds, logs are not shown in most scenarios
Bug: 315285692
Change-Id: I2ec3fa5872b5c33277e4599aa1d3e355590ff70c
parent 779bb8ef

core/java/android/view/ViewRootImpl.java

+6 −0
Original line number Diff line number Diff line
@@ -11912,6 +11912,12 @@ public final class ViewRootImpl implements ViewParent, 


                if (syncBuffer) {

                    boolean result = mBlastBufferQueue.syncNextTransaction(transaction -> {

                        Runnable timeoutRunnable = () -> Log.e(mTag,

                                "Failed to submit the sync transaction after 4s. Likely to ANR "

                                        + "soon");

                        mHandler.postDelayed(timeoutRunnable, 4L * Build.HW_TIMEOUT_MULTIPLIER);

                        transaction.addTransactionCommittedListener(mSimpleExecutor,

                                () -> mHandler.removeCallbacks(timeoutRunnable));

                        surfaceSyncGroup.addTransaction(transaction);

                        surfaceSyncGroup.markSyncReady();

                    });