New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 606308 link

Starred by 2 users
Status: Assigned
Owner:
creis@chromium.org
Cc:
nyerramilli@chromium.org
p...@chromium.org
█ nasko@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression:Unable to reload the crash chrome://badcastcrash page.

Reported by vku...@etouch.net, Apr 25 2016 
Chrome Version:52.0.2715.0 (Official Build)3fae42f136f929251b627b2ae6300100afc8ab83-refs/heads/master@{#388964} (32/64-bit)
OS:Windows (7, 8, 10), Mac (10.10.5)(10.11.4),Linux (ubuntu 14.04 LTS)

What steps will reproduce the problem?
1.Launch chrome and navigate to internal page like chrome://badcastcrash or chrome://crashdump
2.Click on wrench menu and open 'task manager' via more tools.
3.Select the tab and click on 'end process' button, Reload the page,observe

Actual: Unable to reload the crash internal page.

Expected: Should be able to reload the crash internal page.

This is a regression issue broken in 'M47' and will soon update other info.

Comment 1 by vku...@etouch.net, Apr 25 2016

Labels: hasbisect
Owner: creis@chromium.org
Status: Assigned (was: Unconfirmed)
Manual regression range:
Good Build: 47.0.2507.0 
Bad Build:  47.0.2508.0 

Narrow bisect
https://chromium.googlesource.com/chromium/src/+log/8bf14816cc5ddb301dc6ed65e81e492597d3d2a0..cb6de992880a9dfa6fe6efa00a096956f86a2ed9?pretty=fuller&n=30

Suspecting: 348438 ?
Kindly help to re-assign, if your changes are not cause for this issue.
Actual_Result.mov
1.1 MB Download
Expected_Result.mov
1.0 MB Download

Comment 2 by creis@chromium.org, May 2 2016

Cc: nasko@chromium.org p...@chromium.org
Components: -Internals UI>Browser>Navigation Internals>Core
Labels: -Pri-1 Pri-3
This is probably a WontFix after an intentional change in r348438, since URLs like chrome://badcastcrash aren't actually pages that commit to history, but rather commands to run on the current page.  This has already come up in  issue 541032 .

I'm leaving it open for the moment because chrome://badcastcrash/ isn't behaving quite as I'd expect.  Maybe it's because that page doesn't actually crash unless you build with cfi_vptr=1, so we end up on an error page rather than Aw Snap.

We may be able to make things more consistent between the various debug URLs here, but it's definitely low priority.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 12 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment