[Feed] After destroy() still call consumers, fix scheduler bridge.
Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/1345422, doing a couple of things. 1. Removing the destroy warning comment, as all bridges will need to follow this pattern indefinitely. It is not a temporary comment, and adds significant bulk to any bridge that may become out of sync over time. 2. Call consumers/callbacks immediately with error, null, or default responses. This allows the Feed to take reasonable responses and not hang during shutdown. 3. Fix mistake in scheduler check that was backwards, causing the scheduler to think it perpetually had an outstanding request. Bug: 901414 Change-Id: Ied653541755d5fb1b204c4968e755364cdcece81 Reviewed-on: https://chromium-review.googlesource.com/c/1355614Reviewed-by:Filip Gorski <fgorski@chromium.org> Commit-Queue: Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#612463}
Showing
Please register or sign in to comment