Crash Google Chrome Historic
Reported by
kevin...@gmail.com,
Oct 22 2017
|
||||
Issue descriptionChrome Version (from "Settings > About Google Chrome"):62.0.3202.60 Device Type: (iPad 2, iPhone 4, etc) URLs (if applicable):iphone 7 Behavior in Safari (if applicable): Steps to reproduce: (1) Open Google Chrome App (2) Select in menu Historic (3) Expected result: See the page with all websites I had entered Actual result:Chrome get crash and close all tabs
,
Oct 27 2017
Hi kevinhf4, Is this crash happening every time you open History? By any chance, do you have a Brazil language config on your phone, or browse any Brazilian sites? I'm asking because we've seen a similar issue happening mostly in Brazil. Thanks, Sergio
,
Oct 31 2017
Lindsay/Srikanth can you help reproduce this issue?
,
Oct 31 2017
I tried with iPhone5s and locale set to Brazil. Browsed few websites around brazil using maps. Restaurent sites, movie sites etc. Didnot encounter any crashes. May be if we can get a crash ID from user or any other repro site urls that will be helpful.
,
Oct 31 2017
This appears to be a dupe of issue 707241. We've already tried to repro this unsuccessfully many times. However if the user can provide some reproducible exact repro steps that include the sites listed in history, a video, and sync settings, we could use that info for retesting further.
,
Oct 31 2017
Yes, it seems to be a dupe. We already landed a potential fix for this issue. Though we're not sure about the root cause (and why only Brazil), or if the fix will actually address it. Since we haven't been able to repro we need to wait until M63 is out.
,
Oct 31 2017
Hello, For me its simple to reproduce the error, I am using Iphone 7 1. Open Google Chrome 2. Click in menu (3 litle dots) 3. Select "Histórico" or history in english 4. Google get crash and close the app Google Chrome version : 62.0.3202.70 <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Livre de vírus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> 2017-10-31 18:16 GMT-02:00 s… via monorail < monorail+v2.1177862537@chromium.org>:
,
Oct 31 2017
Can you open a new tab and goto chrome://crashes and send us the crash IDs from this page? If Crash reporting is not enabled, then you have to Goto Settings > Privacy > Send Usage data > Always. Done Now reproduce the problem again, and you should now see a crash id in chrome://crashes.
,
Nov 2 2017
I managed to reproduce this but only once so far on a Simulator. Attached is the crash log after the crash. sczs@ please take a look and see if this crash is any useful. https://drive.google.com/file/d/1DSIgxNXKJhdJ86z12Lc16DoTmyTmJnjJ/view
,
Nov 2 2017
Well actually with a little more consistency now. But right now only on Simulators. I can actually give it a try tomorrow with actual devices. Here is what I tried. Sim:A Launch Chrome and Sign in. Wait for all Sync changes. Turn Off Sync SimB: Launch Chrome and Sign in with same account Open Few tabs (facebook, wikipedia, youtube) Sim:A Open wikipedia Goto Settings Turn Sync ON Sim:B Wait few seconds and Tap Menu -> History App Crashes. This happened everytime I try to open History. But it looks like after some history changes synced properly its no longer crashing. I can give it a try on actual devices later.
,
Nov 7 2017
Any update here Srikanth?
,
Nov 7 2017
I was not able to reproduce on devices so far. Sergio to look into further.
,
Nov 7 2017
We can use this information in order to debug 776111 further if needed. Right now we don't have new information that we think can definitely help, and a patch has been already cherrypicked into M63.
,
Nov 7 2017
And just to be sure, kevinhf4@gmail.com, if you could please follow the instructions provided by Srikanth, it could be really helpful for us to have more certainty about this issue if it still exists after the next release! "Can you open a new tab and goto chrome://crashes and send us the crash IDs from this page? If Crash reporting is not enabled, then you have to Goto Settings > Privacy > Send Usage data > Always. Done Now reproduce the problem again, and you should now see a crash id in chrome://crashes." |
||||
►
Sign in to add a comment |
||||
Comment 1 by olivierrobin@chromium.org
, Oct 27 2017Labels: -Pri-3 Stability-Crash ReleaseBlock-Stable M-63 Pri-2
Owner: sczs@chromium.org
Status: Assigned (was: Unconfirmed)