New issue
Advanced search Search tips

Issue 708725 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
editing-dev@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

chrome://histogram crashes under certain circumstances

Project Member Reported by yigu@chromium.org, Apr 5 2017 
Chrome Version: 59.0.3064.0 (Developer Build) (64-bit)
OS: (e.g. Linux)

What steps will reproduce the problem?
(0) Build chromium in debug mode
(1) Open any page that has scrollable areas and scroll one of them
(2) Open chrome://histogram and Ctrl-F search for mainthreadwheel
(3) Go back to the page from the Step 1 and scroll again
(4) Go back to the chrome://histogram tab and refresh


What happens instead?

Crash with error message:

Check failed: m_base.document() == document (#document vs. #document)Selection(base: #text "Histogram: Renderer4.MainThreadWheelScrollReason recorded 248 samples, mean = 1.3 (flags = 0x41)"@offsetInAnchor[22], extent: #text "Histogram: Renderer4.MainThreadWheelScrollReason recorded 248 samples, mean = 1.3 (flags = 0x41)"@offsetInAnchor[32])

Refresh again could fix the problem.

Comment 1 by estaab@chromium.org, Apr 5 2017

Components: -Infra
Labels: -Hotlist-Infra-DX
The infra component is for things like build and test services (buildbot, sheriff tools, flakiness dashboard) not working. You probably need to contact the team who owns the histogram code.

Comment 2 by yigu@chromium.org, Apr 6 2017

Owner: yosin@chromium.org
yosin@, can you take a look at this issue? The check that crashed was added in this patch https://codereview.chromium.org/2393403002/

Comment 3 by yosin@chromium.org, Apr 13 2017

Components: Blink>Editing>Selection
Owner: ----
Status: Available (was: Untriaged)
It seems we don't clear selection before reloading the page.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 13 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

Comment 5 by yosin@chromium.org, Apr 18 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment