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

Issue 646293 link

Starred by 3 users
Status: WontFix
Owner:
steve...@chromium.org
Closed: Nov 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
dpa...@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Tab crashes on continuously reloading chrome://md-settings page using ctrl+R.

Project Member Reported by bj00129...@techmahindra.com, Sep 13 2016 
Version:55.0.2859.0 Dev
OS:Ubuntu 14.04, Chrome-OS

What steps will reproduce the problem?
(1)Launch chrome>> Navigate to chrome://md-settings>>Now hold Ctrl+R for 30 to 60 secs and Observe tab crash.(Please refer video)

Expected: Tab should not crash on continuously reloading the page using ctrl+R.
Actual: Instead tab crash is seen.

Crash ids: 51abad7500000000,3beaec7500000000

Note: 
1.Try once again if you cannot see the crash in the first attempt.
2.This issue is also seen in 55.0.2857.0/8793.0.0 dev channel gnawty.
3.This issue is not seen in windows.

This is Regression issue broken in M-50.
Good build:50.0.2655.0 Dev
Bad build:50.0.2656.0 Dev

CHANGELOG URL:  https://chromium.googlesource.com/chromium/src/+log/4b12c0a123b31adcccb095cb2a49ca7b59f9f1fb..f308ba69c656143f287e565181c1feaa7725edf7

Suspecting  https://codereview.chromium.org/1666623006 from changelog.

@dpapad: Please help in re-assigning if it is not related to your change.

Attaching screen-cast for reference.
Actual_Tabcrash.ogv
2.3 MB View Download

Comment 1 by ajha@chromium.org, Sep 13 2016

Labels: -Pri-1 Pri-2
Somehow I am unable to reproduce the issue on 55.0.2859.0 on Linux Ubuntu 14.04 and Mac OS 10.11.6.

Providing the stack trace of attached crash id(51abad7500000000) from Linux for further investigation:

Thread 0 CRASHED [SIGILL @ 0x00007f13acee0cbb ] MAGIC SIGNATURE THREAD
0x00007f13acee0cbb	(chrome -./out/Release/../../build/linux/debian_wheezy_amd64-sysroot/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/unique_ptr.h:63 )	<name omitted>
0x00007f13ab56f200	(chrome -./out/Release/../../url/url_util.cc:209 )	DoCanonicalize<char>
0x00007f13a9740d03	(chrome -./out/Release/../../third_party/tcmalloc/chromium/src/thread_cache.h:201 )	do_free_with_callback
0x00007f13ae50bf01	(chrome -./out/Release/../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1045 )	tc_malloc
0x00007f13a9738449	(chrome -./out/Release/../../base/allocator/allocator_shim.cc:163 )	ShimCppNew
0x00007f13a28d23b8	(libstdc++.so.6.0.19 + 0x000ba3b8 )	
0x00007f13a28d3b2d	(libstdc++.so.6.0.19 + 0x000bbb2d )	
0x00007f13ab562c79	(chrome -./out/Release/../../url/gurl.cc:382 )	<name omitted>
0x00007f13aea40a54	(chrome + 0x05e0ea54 )	_fini
0x00007f13ac940f44	(chrome -./out/Release/../../content/child/web_url_loader_impl.cc:724 )	content::WebURLLoaderImpl::Context::OnReceivedResponse
0x00007f13a99e3f0e	(chrome -./out/Release/../../v8/src/heap/incremental-marking-inl.h:18 )	<name omitted>
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 14 2016

Labels: Fracas FoundIn-M-55
Users experienced this crash on the following builds:

Linux Dev 55.0.2859.0 -  18.77 CPM, 3 reports, 1 clients (signature DoCanonicalize<char>)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Comment 3 by dpa...@chromium.org, Sep 20 2016

Labels: -Pri-2 Pri-3
Status: Untriaged (was: Assigned)
I doubt that r376362 is related to this crash. None of the contents of chrome://md-settings/searchEngines is loaded when landing on chrome://md-settings.

I am unassigning myself to let this bug be triaged properly. FWIW, I was able to make the tab crash once, out of multiple attempts. Given that this bug requires the user refreshing for 30/60 seconds, I think in is a P3.

Comment 4 by dpa...@chromium.org, Sep 20 2016

Cc: dpa...@chromium.org
Owner: ----

Comment 5 by steve...@chromium.org, Oct 14 2016

Labels: -Pri-3 Pri-1
Owner: steve...@chromium.org
Status: Assigned (was: Untriaged)
I'll see if I can repro this on Monday. It's either a P1 if we can repro of a WontFix if not (it will show up in the crash reports if there is a scenario where it can be reproduced).

Comment 6 by steve...@chromium.org, Nov 11 2016

Status: WontFix (was: Assigned)
Can't repro on ToT. A lot has changed since 55.
►

Sign in to add a comment