Issue metadata
Sign in to add a comment
|
crash on specific website *.instructure.com |
||||||||||||||||||||||
Issue descriptionChromeOS version: 69.0.3497.95 ChromeOS device model: Lenovo 300e/N23 Yoga/Flex 11 Chromebook (hana) Case#: 17059808 Description: when the customer logins on a site made by instructure.com they have a crash. Steps to reproduce: login to any site made by instructure.com Current Behavior / Reproduction: crash Expected Behavior: with 68.0.3440.118 there is no Crash Drive link to logs: https://drive.google.com/open?id=1XkYwHJGQaaKajkdEYINfkgN9T1KGQEti https://drive.google.com/open?id=1iK51WQfAHAU557LE_zrA5ZxvJk1GKgtM policies: https://drive.google.com/open?id=1FZEZnNKQtv2s76y9b0rRnbveIX6YCiIM crashes: b6f03b7e9182a176 6bad930cdea34741 5ec9e62161f86569 59d7be9ee2c9a46b 2320992586eaeb79 dac1fc33b72b2fec 35d5df79b90ce55f f173b6af14353dea 922bc5892b6ce3f2 cf26338d9f813430 d81e3026c1d67b38 a7a9a13e65beee64 fb8b4e71438258d0 a1d8907ac97a96fb Stable Signature: icu_62::UnicodeSet::UnicodeSet-993dc5d5 on one of the affected user I see: intl.accept_languages "value": "\"en-US,ko\""
,
Oct 3
Customer info and specific site with the issue: https://drive.google.com/open?id=1NusGUfD2ySz5JCBp7p3lSRHXzHecpl_zZ_jorJeEhTs save as of html page with the issue https://drive.google.com/open?id=1vMSZjDD3_-QAYEddl3Z04ghiygLLrFQU we are gathering more information: - video of the issue - HAR file - Chrome://net-export - Chrome://tracing
,
Oct 5
An enterprise customer has reported very similar issue. ChromeOS version: 69.0.3497.95 ChromeOS device model: Lenovo N23 Yoga Case#: 17102316 The customer has reported: The users are getting an Aw Snap page when accessing bisonpride.instructure.com on their Chromebook. But if we sign them into another Chromebook(HP g5) or chrome browser on PC works. Error message:Aw, Snap! Something went wrong while displaying this webpage Steps to reproduce: login to any site made by instructure.com Current Behavior / Reproduction: crash Inspection Notes. wiped the device. deleted the user from the device and still nothing. connected it to an open network to make sure it was not my filtering still nothing Drive link to logs: Device log.https://drive.google.com/open?id=1pvcng9Ty0sc6-gTUAOaRL3um8HV2iqdL crashes: https://drive.google.com/open?id=1cB7G064cQhXglMO7QXpmq-iWrBCv6BoS Cf363e7b9734098b (Stable Signature: icu_62::UnicodeSet::UnicodeSet-993dc5d5) 310ee5df704e156f (Stable Signature:icu_62::UnicodeSet::UnicodeSet-993dc5d5) Customer info and specific site with the issue: https://drive.google.com/open?id=1sM-kC7MHqxPp5uesg0aaYplpZDgOftM9DS9oeMkGLsI
,
Oct 10
Here is another report: https://listnr.corp.google.com/product/208/report/85713187 and I believe it's one of these crashes: https://crash.corp.google.com/browse?q=product_name%3D%27Chrome_ChromeOS%27+AND+product.Version%3D%2769.0.3497.95%27+AND+expanded_custom_data.ChromeCrashProto.ptype%3D%27renderer%27+AND+STRPOS%28expanded_custom_data.ChromeCrashProto.url.simplified%2C+%27canvas%27%29+%3E+0+AND+expanded_custom_data.ChromeCrashProto.url.simplified%3D%27https%3A%2F%2Fcanvas.csun.edu%2F*%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27icu_62%3A%3AUnicodeSet%3A%3AUnicodeSet%27 jshin@, can you look into these?
,
Oct 11
We're seeing a lot of feedback reports from users about this on elm (acer chromebook 13) https://listnr.corp.google.com/report/85714455501 : http://canvas.ljmu.ac.uk/ https://listnr.corp.google.com/report/85714595483 : https://colostate.instructure.com/?login_success=1 https://listnr.corp.google.com/report/85715184632 : https://iowacconline.instructure.com/?login_success=1 https://listnr.corp.google.com/report/85715121359 : https://thomasmoreky.instructure.com/ https://listnr.corp.google.com/report/85715184632 : https://iowacconline.instructure.com/?login_success=1 https://listnr.corp.google.com/report/85715163423 : https://canvas.uva.nl/ https://listnr.corp.google.com/report/85714220757 : https://canvas.ubc.ca/ https://listnr.corp.google.com/report/85713538874 : https://canvas.csun.edu/ https://listnr.corp.google.com/report/85712402644 : https://canvas.uva.nl/ https://listnr.corp.google.com/report/85711305754 : https://canvas.csun.edu/?login_success=1 https://listnr.corp.google.com/report/85711279048 : https://nmsu.instructure.com/?login_success=1 https://listnr.corp.google.com/report/85711171717 : https://canvas.instructure.com/?login_success=1 and many more. I think there are > 50 feedback reports submitted to https://groups.google.com/a/google.com/forum/#!forum/elm-feedback-reports in the past week alone on this. Upping the priority.
,
Oct 11
Adding the M69 and M70 TPMs govind@ and abdulsyed@ - can you please help find an appropriate owner? We're seeing a lot of reports from users.
,
Oct 12
This crash is reported on Chrome OS, so adding Chrome OS M69 and M70 TPMs( cindyb@ & geohsu@).
,
Oct 12
+djkurtz, dianders since we're seeing this primarily on oak/veyron/gru devices Dan/Doug, can you help narrow this down so we can find an owner to fix this? We're seeing quite a few reports every day. https://listnr.corp.google.com/product/208/reports?searchText=canvas&filter=0&dateRange=All
,
Oct 14
@#8 - From crash stats, it looks like it is the crash is *not* on veyron, and just on oak [elm, hana] & gru [kevin, dru] (ie, our arm64 boards). This arch dependency makes me suspect V8. https://crash.corp.google.com/browse?q=product_name%3D%27Chrome_ChromeOS%27+AND++expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27icu_62%3A%3AUnicodeSet%3A%3AUnicodeSet%27#-propertyselector,-productname:1000,-magicsignature:50,-directory,-magicsignature2:50,-stablesignature:50,-clientid,devicemodel,url,-country,-magicsignaturesorted:50 It was introduced sometime before 69.0.3497.58.
,
Oct 14
A wild guess could be this CL [0], but I don't know an easy way to figure out in which (R69) Chrome OS version it landed: https://chromium.googlesource.com/chromium/deps/icu/+/297a4dd02b9d36c92ab9b4f121e433c9c3bc14f8
,
Oct 14
The CL referred actually fixed a crash by providing correct alignment otherwise Chrome didn't even reach login screen. Based on https://unicode-org.atlassian.net/browse/ICU-20001, more places needed a similar fix, not sure if that was done or not in Chrome 69.
,
Oct 15
Re:#9 - https://listnr.corp.google.com/product/208/report/85717555903 was on veyron_minnie, but maybe that's a different crash?
,
Oct 15
strange, this is on gnawty: https://listnr.corp.google.com/product/208/report/85713349272 But yes, the vast majority of issues are on gru and oak gnawty and veyron may be one-offs that are unrelated
,
Oct 16
If you believe V8 might be the cause, please add the JavaScript component. Infra>V8 is for V8's infrastructure only.
,
Oct 16
,
Oct 23
cindyb@ and geohsu@ - can you please help find an owner for this? we are seeing lots of user complaints here
,
Oct 25
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by edoan@chromium.org
, Oct 2