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

Commit 3ab499df authored by Jayant Chowdhary's avatar Jayant Chowdhary
Browse files

cameraserver: Reduce Camera2ClientBase destructor log confusion.



We log disconnect in CameraService::BasicClient::disconnect() and also
in ~Camera2ClientBase(). Since ~Camera2ClientBase() can often run a few
seconds after BasicClient::disconnect(depending on when we get another
binder call), the disconnect logs from the Camera2ClientBase destructor
can be confusing to look at on quick inspection.

Bug: 235352466

Test: Inspect logs

Change-Id: I3fbaa0bde2c21c3b13d5d86f7691eb49f9eb53a2
Signed-off-by: default avatarJayant Chowdhary <jchowdhary@google.com>
parent 8199b3f7
Loading
Loading
Loading
Loading
+2 −2
Original line number Diff line number Diff line
@@ -168,8 +168,8 @@ Camera2ClientBase<TClientBase>::~Camera2ClientBase() {
        mCameraServiceWatchdog.clear();
    }

    ALOGI("Closed Camera %s. Client was: %s (PID %d, UID %u)",
            TClientBase::mCameraIdStr.string(),
    ALOGI("%s: Client object's dtor for Camera Id %s completed. Client was: %s (PID %d, UID %u)",
            __FUNCTION__, TClientBase::mCameraIdStr.string(),
            String8(TClientBase::mClientPackageName).string(),
            mInitialClientPid, TClientBase::mClientUid);
}