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

Commit ef671105 authored by Philip Cuadra's avatar Philip Cuadra
Browse files

Remove tracing for notifyContentCapture

These traces get expensive in aggregate due to an increased number of
notifyContentCapture events.  Remove them.

Bug 188836620
Test:  Confirmed no notifyContentCapture trace points in systrace

Change-Id: I5d77bd9048b2e8cd267187f866dc095792a3f455
parent d8be4517
Loading
Loading
Loading
Loading
+1 −15
Original line number Diff line number Diff line
@@ -9808,23 +9808,9 @@ public class View implements Drawable.Callback, KeyEvent.Callback,
     */
    private void notifyAppearedOrDisappearedForContentCaptureIfNeeded(boolean appeared) {
        AttachInfo ai = mAttachInfo;
        // Skip it while the view is being laided out for the first time
        // Skip it while the view is being laid out for the first time
        if (ai != null && !ai.mReadyForContentCaptureUpdates) return;
        if (Trace.isTagEnabled(Trace.TRACE_TAG_VIEW)) {
            Trace.traceBegin(Trace.TRACE_TAG_VIEW,
                    "notifyContentCapture(" + appeared + ") for " + getClass().getSimpleName());
        }
        try {
            notifyAppearedOrDisappearedForContentCaptureIfNeededNoTrace(appeared);
        } finally {
            Trace.traceEnd(Trace.TRACE_TAG_VIEW);
        }
    }
    private void notifyAppearedOrDisappearedForContentCaptureIfNeededNoTrace(boolean appeared) {
        AttachInfo ai = mAttachInfo;
        // First check if context has client, so it saves a service lookup when it doesn't
        if (mContext.getContentCaptureOptions() == null) return;