| commit | 64b3e6e90311e5221460ecee0655a148df3026c1 | [log] [tgz] |
|---|---|---|
| author | Jerome Gaillard <jgaillard@google.com> | Thu Aug 31 17:49:56 2023 +0100 |
| committer | Cherrypicker Worker <android-build-cherrypicker-worker@google.com> | Fri Sep 01 11:26:39 2023 +0000 |
| tree | 173a7e3d3ffb15ca532b0173b848c893f3b4597a | |
| parent | 829217ebc537878f990c2f7aa88f3272266a651e [diff] |
Use ApplicationContext to create BridgeContentResolver BridgeContentResolver holds a reference to the context that is used to create it. This means that if user/library code stores a content resolver, that can lead to a leak of the BridgeContext. To prevent this, we create BridgeContentResolver with the ApplicationContext, which only holds a weak reference to the BridgeContext. Bug: 290990640 Test: N/A (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:044f194cf028afac353634b618a486110d9feb52) Merged-In: Ib5a5429d2bb11a75dc5ecfdf20effc98b797a2cc Change-Id: Ib5a5429d2bb11a75dc5ecfdf20effc98b797a2cc