Issue metadata
Sign in to add a comment
|
Chrome tab hard crash when user clicks a button within an angular webapp
Reported by
igor.jac...@gmail.com,
Mar 26 2018
|
||||||||||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Open website (it's internal), that is angular 1.6 based. 2. Click on continue button 3. A pop tab window is opened. 4. A bootstrap modal/confirmation dialog ask the user if he wants to continue. 5. Clicking yes button. What is the expected behavior? The tab/application keeps working, no tab crash. After the user confirms, a HTTP POST request saving the form is done as usual, and the user is back to his portal page. What went wrong? The tab crashes and has to be reloaded, potential lost of data as its a hard crash. Crashed report ID: 2ce9ea65-34cc-4676-bb78-e2f849f089ab How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? Yes Chrome 64 Chrome version: 65.0.3325.181 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Crashes seem to appeared since Chrome 65.3325.162 They are random, but happen up to 10 times per day, sometimes 2-3. OS: Windows 7 I have attached several dump files that I got from chrome://crashes from 2 uers.
,
Mar 27 2018
Ah, ok then I got plenty of those. 2 more crashes today morning (the browser is in german): Abstürze (2) Lokale Absturz-ID: df4e5c22-77c3-465d-9d7f-0b7ededa1325 Absturzbericht erfasst am Dienstag, 27. März 2018 um 07:48:37 Lokale Absturz-ID: d2e72fcc-c6af-44c4-b3d3-1cb7889d78a3 Absturzbericht erfasst am Dienstag, 27. März 2018 um 07:41:49
,
Mar 27 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 27 2018
Forgot to mention to my last comment, in the user machine the auto-upload of crashes is not enabled, therefore I used the "Report an issue button" I wrote there a reference to this bug. The local crash Id is either: df4e5c22-77c3-465d-9d7f-0b7ededa1325 or d2e72fcc-c6af-44c4-b3d3-1cb7889d78a3
,
Mar 27 2018
I just saw one more crash 3min ago. Lokale Absturz-ID: 24756b06-b836-4630-b9ba-f584b6c9a8a3 Absturzbericht erfasst: Dienstag, 27. März 2018 um 09:50:16 (Upload wurde vom Nutzer angefordert, aber noch nicht abgeschlossen) I enabled the auto-upload of crashes in that machine's browser. I once again used the "Report an issue" button to report the problem and referenced this bug there. I did not see locally the dmp file, a bit strange. I have notice that the popup that the main page creates stop loading the page. (but no crash there), only the main page crashes.
,
Mar 28 2018
Thanks for the update. We are looking for crash id as attached in the screenshot here. Please confirm if any of crashes generated under chrome://crashes show such Crash Report ID. Also would it be possible to share any sample test file(shareable externally) to test and bisect this from our end.
,
Mar 28 2018
Hi, thanks for taking a look and the fast feedback. So far the different computers(3) that I have seen not, only local crashes. I asked a college of mine to see if he can get such one Id, in a computer that had chrome with auto-report enabled. I have also click to send the local crashes, but only says upload requested but not yet done. Surprisingly, seems a bit tricky to get the report Id. Have the the many dump files help you? Also 2 times I used the "Report Issue" button, adding/referencing this address: https://bugs.chromium.org/p/chromium/issues/detail?id=825799 I assume that gives you extra information that you need. (see my new screenshot) Sorry, its really a terrible bug, more than 50 people are having the issue, and only workaround is to use Chrome 64, or use Firefox.
,
Mar 28 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 28 2018
About the any sample test file(shareable externally) to test. Does not make sense to extract. Its a relatively big Angular 1.6/boostrap web application, we try to use latest libraries. Besides a memory leak 1 year ago, and a pdf.js plugin that we stop using/uninstalled because was too slow for large PDFs, we never any such issues for 3 years 3 months. there is an ng-click that then opens a boostrap dialog when the promise completes, an http POST request is triggered, when http promise completes, we load another page, the landing page.
,
Apr 17 2018
Tentativle adding Enterprise label based on C#8 for someone from the respective team to help in triaging this further. I am not seeing anything suspicious in the systemlog for the feedback report attached to this bug. Link to the feedback reports: https://goto.google.com/xaknc https://goto.google.com/ellby Could anyone facing this issue, also check the same in the latest beta(https://www.chromium.org/getting-involved/dev-channel) and confirm if the issue still persists. Also, check by disabling all the extensions.
,
Apr 18 2018
CC'ing enterprise dev julian@ for further triage
,
Apr 20 2018
Not clear why this is Enterprise related. Definitely worth looking at the dmp files in the absence of a publicly accessible repro case - Julian, is this a thing you can do?
,
Apr 20 2018
,
Apr 23 2018
Unable to triage this issue from TE end, hence adding TE-NeedsTriageHelp label for further triage. Could someone from Dev team look into this issue.
,
May 3 2018
Thank you so much for your efforts. We really did suffer a lot with the problem. At the end our the only workaround was to downgrade Chrome 64 or use the Chrome Beta 66, or use FF. The crashing completely/magically stopped appearing in Chrome 66. So only Chrome 65 was unstable for us. Unfortunately the root cause was not clear nor found. Please tellme/decide if you think its better to close the issue, as it was only reproducible in Chrome 65. |
|||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||
Comment 1 by igor.jac...@gmail.com
, Mar 26 2018