When constructing cyclic proxies share an invocation handler across all allocated proxies.#1855
Closed
copybara-service[bot] wants to merge 0 commit intomasterfrom
Closed
When constructing cyclic proxies share an invocation handler across all allocated proxies.#1855copybara-service[bot] wants to merge 0 commit intomasterfrom
copybara-service[bot] wants to merge 0 commit intomasterfrom
Conversation
copybara-service
bot
force-pushed
the
test_713820950
branch
from
b3b3270 to
c5e7d93
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When constructing cyclic proxies share an invocation handler across all allocated proxies.
Additionally optimize the implementation of DelegatingInvocationHandler to eliminate an unnecessary field
With these two optimizations in place, the maximum size of a leak from resolving multithreaded lock cycles in SingletonScope is now a single tiny object, so instead of eagerly clearing out proxies to avoid a leak we can just wait to satisfy them if someone attempts to construct the singleton a second time, and if we don't we just won't sweat these 16 bytes.