Delete scoped_refptr of PasswordProtectionRequest
The PasswordProtectionService and PasswordProtectionNavigationThrottle both own a scoped_refptr to PasswordProtectionRequest. When both the Service and Throttle class are created, two scoped_refptrs are created for the same PasswordProtectionRequest. When the request is finished, the Service class erases the scoped_reptrs, but the Throttle class still contains a reference to the scoped_refptr, which causes a page hang. Thus, the Throttle class also needs to release the scoped_refptr when navigation is resumed or canceled. A follow up is to refactor the PasswordProtectionRequest and not have it RefCounted. Bug: 1110427 Change-Id: Idf66b0451036099d0a417a42b6a37f5a5b10cf13 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406599 Commit-Queue: Bettina Dea <bdea@chromium.org> Reviewed-by:Varun Khaneja <vakh@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/master@{#811911}
Showing
Please register or sign in to comment