Crash after clicking X to dismiss a notification Beta 67
Reported by
dymp...@gmail.com,
May 5 2018
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10575.22.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.26 Safari/537.36 Platform: 10575.22.0 (Official Build) beta-channel caroline Steps to reproduce the problem: 1. open notification/message center 2. click on X to dismiss What is the expected behavior? Notification is dismisses What went wrong? Cash All other notifications were lost, even after clicking on "restore". Crashed report ID: Uploaded Crash Report ID 8da0af8e2332621d (Local Crash ID: Chrome) Crash report uploaded on Saturday, May 5, 2018 at 1:17:01 PM How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 67.0.3396.26 Channel: beta OS Version: 10575.22.0 Flash Version: 29.0.0.168 Feedback sent: Crash from clicking on X to dismiss a notification Beta 67. Other notifications are lost after clicking "restore" 1:06 pm EDT 5/5/2018 1. sleep overnight > open lid 2. notifications pop up 3. click on X to dismiss 4. crash 5. restore Chrome OS > did not restore the other notifications From Asus Flip: Crash caused by clicking on X to dismiss a notification. 11:22 am EDT I think it was a Android Calendar app notification chrome://crashes does not show a crash Google Chrome 67.0.3396.26 (Official Build) beta (32-bit) Revision de708ace5575abaacda89a3ae16cbad2cde45696-refs/branch-heads/3396@{#369} Platform 10575.22.0 (Official Build) beta-channel veyron_minnie Firmware Version Google_Veyron_Minnie.6588.237.0 ARC 4749218 JavaScript V8 6.7.288.23 Flash 29.0.0.168 /opt/google/chrome/pepper/libpepflashplayer.so User Agent Mozilla/5.0 (X11; CrOS armv7l 10575.22.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.26 Safari/537.36
,
May 5 2018
Verified on: Google Chrome 67.0.3396.26 (Official Build) beta (64-bit) Revision de708ace5575abaacda89a3ae16cbad2cde45696-refs/branch-heads/3396@{#369} Platform 10575.22.0 (Official Build) beta-channel auron_yuna Firmware Version Google_Auron_yuna.6301.59.116 ARC 4749218 JavaScript V8 6.7.288.23 Flash 29.0.0.168 /opt/google/chrome/pepper/libpepflashplayer.so
,
May 5 2018
#CBC-RS/TC-watchlist
,
May 5 2018
Dismissing a screenshot notification does not cause a crash.
,
May 6 2018
For me, dismissing notifications from android apps via x button always ends up with a whole UI crashing on 67 beta.
,
May 6 2018
Crash after swiping as well now on Beta 67 827850 - Swiping away notification launches the app when the notification should simply be swiped away. - chromium - Monorail https://bugs.chromium.org/p/chromium/issues/detail?id=827850
,
May 7 2018
,
May 11 2018
See Crash ID: crash/811a99c31b73cd6e Still happening on Version 67.0.3396.41 (Official Build) beta (64-bit)
,
May 11 2018
Ticket was merged as a duplicate into 836523 but the other bug report is not viewable. Does that mean it's already being worked on?
,
May 11 2018
Swiping doesn't crash for me, it just opens the app still, but clicking the x to dismiss any notification definitely causes the whole UI to crash.
,
May 15 2018
Can someone please address this bug? It has been happening for weeks and has not been addressed. UI now crashes when Android notifications are swiped away.
,
May 15 2018
The worst part is we don't even know if it's being worked on as it's been merged into another bug that no one can even see.
,
May 15 2018
I found this, but I'm not sure how helpful it is: https://chromium.googlesource.com/chromium/src/+/cdda1da1392591ea4aaf01b24be0802bdef85214
,
May 15 2018
I take it back swiping does indeed cause a crash... if you angle it downwards. Otherwise, swiping slightly upwards causes the app to open instead of triggering the close action. Dismissing any notification, in any way, causes a crash it seems. This is pretty bad, as it can cause data loss if all work isn't saved. Dismissing a notification should not crash the whole UI and kill all open applications, even on Android runtime.
,
May 15 2018
836523 probably has user data in a crash report, so it's been made private. I assume this is being worked on... Any idea when we can expect the fix to be pushed out in a release? |
||
►
Sign in to add a comment |
||
Comment 1 by dymp...@gmail.com
, May 5 2018