When I looked into this on Jun 1 for https://codereview.chromium.org/2918023002/ I observed CompositorImpl::SetVisible was being called, did you observe differently?  Might be a recent regression if so?

Actually you are right, it gets called when I test manually. Somehow it is not set in the benchmark causing  issue 747031 . I will get more info on this soon.

So, the issue is the CompositorImpl::SetVisible should be called by android window callback dispatching at android.view.SurfaceView.updateWindow.
But Android system only destroys the surface if the app goes to background and not if the power button is pressed when app is in foreground.
But, application's activities are destroyed on both cases when the application becomes invisible.

This causes the CompositorImpl to not know that the app is invisible but, the activities destroyed notification tries to clear the gl memory and recreates because the surface is not destroyed.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Assigning to ericrk for Android/compositor triage.