forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Extensions] Properly dispose of GCCallback in context invalidation
If the Context is invalidated before the object GCCallback is watching is collected, a fallback is run and the original callback (for garbage collection) is never triggered. There was a bug where we only properly disposed of GCCallback (thus preventing it from triggering after the context invalidated) if a non-null fallback was provided. Fix this, properly cleaning up the GCCallback even with a null fallback, and add unit tests to cover this case. Bug: 808032 Change-Id: I0e17dfcec7d796883bc1b59bf450c86d3e79ac99 Reviewed-on: https://chromium-review.googlesource.com/898071 Reviewed-by: Jeremy Roman <jbroman@chromium.org> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#533809}
- Loading branch information
Showing
2 changed files
with
32 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters