BluetoothRemoteGATTServer: remove context observer and prefinalizer
With the default HeapMojoRemote setting there was a bad interaction between service_ and the GATTServer cleanup. service_ would get cleaned up in its own OnContextDestroyed method but then the GattServer would try to access it in Dispose. This was worked around by using kForceWithoutContextObserver. In BluetoothGATTServer there should not be any need for manual cleanup: service_ can use the OnContextDestroyed method and the other object being cleaned up, active_algorithms_, is a HeapHashSet with its own associated garbage collection. Bug: 1049056 Change-Id: Ia81e99743c1f8bdccf37b54d0761258571a3ad4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275515Reviewed-by:Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Johann Koenig <johannkoenig@google.com> Cr-Commit-Position: refs/heads/master@{#788852}
Showing
Please register or sign in to comment