|
|
Chromium Code Reviews
DescriptionFix crash caused by stale WebContents in chrome://interstitials
InterstitialHTMLSource provides the data for this page using the
wrong WebContents. This isn't a problem when the links are opened in the
same tab. However, when a link is opened in a new tab, web_contents_ of
IntersititalHTMLSource is assigned to the new tab. When the tab is destroyed,
future data requests are made using the stale web_contents and cause a crash.
Instead, simply use the WebContents provided in
InterstitialHTMLSource::StartDataRequest.
BUG=611706
Committed: https://crrev.com/861833fc6f49583b3fb052c6711c3733d1478a42
Cr-Commit-Position: refs/heads/master@{#425185}
Patch Set 1 #
Messages
Total messages: 18 (11 generated)
Description was changed from ========== Fix crash caused by stale WebContents in chrome://interstitials InterstitialHTMLSource that provides the data for this page uses the wrong WebContents. This isn't a problem when the links are opened in the same tab. However, when a link is opened in a new tab, web_contents_ of IntersititalHTMLSource is assigned to the new tab. When the tab is destroyed, future data requests are made using this stale web_contents and cause a crash. Instead, simply use the WebContents provided in InterstitialHTMLSource::StartDataRequest. BUG=611706 ========== to ========== Fix crash caused by stale WebContents in chrome://interstitials InterstitialHTMLSource provides the data for this page using the wrong WebContents. This isn't a problem when the links are opened in the same tab. However, when a link is opened in a new tab, web_contents_ of IntersititalHTMLSource is assigned to the new tab. When the tab is destroyed, future data requests are made using the stale web_contents and cause a crash. Instead, simply use the WebContents provided in InterstitialHTMLSource::StartDataRequest. BUG=611706 ==========
meacer@chromium.org changed reviewers: + estark@chromium.org
estark: PTAL? Thanks.
The CQ bit was checked by meacer@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm but how hard would it be to write a regression test?
On 2016/10/13 21:14:09, estark wrote: > lgtm but how hard would it be to write a regression test? There are browser tests for this code but they are disabled (interstitial_ui_browsertest.cc). How about I try reenabling them and and a regression test for this in another CL?
On 2016/10/13 21:18:30, Mustafa Emre Acer wrote: > On 2016/10/13 21:14:09, estark wrote: > > lgtm but how hard would it be to write a regression test? > > There are browser tests for this code but they are disabled > (interstitial_ui_browsertest.cc). How about I try reenabling them and and a > regression test for this in another CL? Ok, sgtm
The CQ bit was checked by meacer@chromium.org
The CQ bit was unchecked by meacer@chromium.org
The CQ bit was checked by meacer@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Fix crash caused by stale WebContents in chrome://interstitials InterstitialHTMLSource provides the data for this page using the wrong WebContents. This isn't a problem when the links are opened in the same tab. However, when a link is opened in a new tab, web_contents_ of IntersititalHTMLSource is assigned to the new tab. When the tab is destroyed, future data requests are made using the stale web_contents and cause a crash. Instead, simply use the WebContents provided in InterstitialHTMLSource::StartDataRequest. BUG=611706 ========== to ========== Fix crash caused by stale WebContents in chrome://interstitials InterstitialHTMLSource provides the data for this page using the wrong WebContents. This isn't a problem when the links are opened in the same tab. However, when a link is opened in a new tab, web_contents_ of IntersititalHTMLSource is assigned to the new tab. When the tab is destroyed, future data requests are made using the stale web_contents and cause a crash. Instead, simply use the WebContents provided in InterstitialHTMLSource::StartDataRequest. BUG=611706 ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== Fix crash caused by stale WebContents in chrome://interstitials InterstitialHTMLSource provides the data for this page using the wrong WebContents. This isn't a problem when the links are opened in the same tab. However, when a link is opened in a new tab, web_contents_ of IntersititalHTMLSource is assigned to the new tab. When the tab is destroyed, future data requests are made using the stale web_contents and cause a crash. Instead, simply use the WebContents provided in InterstitialHTMLSource::StartDataRequest. BUG=611706 ========== to ========== Fix crash caused by stale WebContents in chrome://interstitials InterstitialHTMLSource provides the data for this page using the wrong WebContents. This isn't a problem when the links are opened in the same tab. However, when a link is opened in a new tab, web_contents_ of IntersititalHTMLSource is assigned to the new tab. When the tab is destroyed, future data requests are made using the stale web_contents and cause a crash. Instead, simply use the WebContents provided in InterstitialHTMLSource::StartDataRequest. BUG=611706 Committed: https://crrev.com/861833fc6f49583b3fb052c6711c3733d1478a42 Cr-Commit-Position: refs/heads/master@{#425185} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/861833fc6f49583b3fb052c6711c3733d1478a42 Cr-Commit-Position: refs/heads/master@{#425185} |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
