Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
SyncableServiceBasedModelTypeController: Handle null SyncableService
It turns out that in some cases, the SyncableService passed into SyncableServiceBasedModelTypeController may be null - in particular, this may happen for HistoryDeleteDirectivesModelTypeController if the HistoryService is null (which can happen e.g. if its database initialization failed). This CL fixes the issue by handling null within SyncableServiceBasedModelTypeController's ControllerDelegate. (cherry picked from commit e145a12) Bug: 1394815 Change-Id: I959ed706c3feb12b318b5861866a945b392195eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4075804 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by: Mikel Astiz <mastiz@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1078663} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4083728 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Srinivas Sista <srinivassista@chromium.org> Owners-Override: Srinivas Sista <srinivassista@chromium.org> Cr-Commit-Position: refs/branch-heads/5359@{#1104} Cr-Branched-From: 27d3765-refs/heads/main@{#1058933}
- Loading branch information