Descriptionaw: Fix detach and destroy interaction
Previously we cannot destroy native side before detach because we would
have leaked hardware resources. This is no longer the case ever since
requestDrawGL takes a waitForCompletion parameter. Now we can
synchronously call nativeOnDetachedFromWindow from inside destroy to
clean up hardware resources, and then actually destroy native side
immediately.
Then also found that AwSettings will crash after destroying native since
it does not always check that the native pointer is not 0. Fixed these
and added a test.
BUG=
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=268034
Patch Set 1 #
Total comments: 4
Patch Set 2 : fix comment #Patch Set 3 : rebase #
Messages
Total messages: 12 (0 generated)
|