More diagnostics for tracking opaque request_initiator_site_lock.
Most DwoC reports for https://crbug.com/1056949 seem to indicate that the request_initiator_site_lock has been set to an opaque, unique origin. This CL tweaks two code paths that can lead to such an opaque origin: 1. mhtml subframes 2. committing a browser-initiated navigation to an about:blank URL After this CL, the origins above will be derived from an artificial origin that should show up in crash keys of DwoC reports. This CL supplements r779447 which so far has come back empty handed. Bug: 1056949 Change-Id: I0b6eeb266ebe4d625b2a9a949f6fec0710872c92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2273486 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#783795}
Showing
Please register or sign in to comment