Issue metadata
Sign in to add a comment
|
Crash browser on startup due to colliding notification types values
Reported by
ivafa...@yandex-team.ru,
Mar 15 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 YaBrowser/18.3.1.349 Yowser/2.5 Safari/537.36 Steps to reproduce the problem: Start a browser with fully loaded v4 safe browsing databases. This crash is a bit problematic to reproduce locally so as it relates to a race condition. What is the expected behavior? Not to crash. What went wrong? Crash Crashed report ID: no How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: 64.0.3282.140 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 29.0 r0 There is a try to fix crash here: https://chromium-review.googlesource.com/c/chromium/src/+/964222
,
Mar 16 2018
,
Mar 16 2018
Hi! I don't have the report ID. I've provided some info about root cause here: https://chromium-review.googlesource.com/c/chromium/src/+/964222 This info should be sufficient for programmers to fix the issue.
,
Mar 16 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 19 2018
CC'ing file reviewer from the CL below https://chromium-review.googlesource.com/c/chromium/src/+/964222 @derat: Could you please help us with this. Thanks!!
,
Mar 19 2018
There's already a discussion on the changelist. Copying jam@'s comment from there: "The notification system has been deprecated for a long time, and the existing method which we avoided collisions between chrome and extensions was already hacky. Instead of adding another hack for one notification in components/safe_browsing, i think we should bring back that notification which was added recently back to src/chrome, and have the component just notify src/chrome which then fires it."
,
Mar 22 2018
Seems it is out of scope from TE end as per C#6, adding TE-NeedsTraige-help label to move this out of our triaging bucket. Could someone from dev team please take a look into this issue. Thanks..!
,
Mar 27 2018
,
Mar 29 2018
This issue was fixed here: https://chromium-review.googlesource.com/c/chromium/src/+/979192 Could please anyone mark the ticket as fixed?
,
Mar 29 2018
,
Mar 30 2018
Happy to have accidentally fixed it! If anyone wants to help slowly remove notifications, please do! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jmukthavaram@chromium.org
, Mar 16 201854.4 KB
54.4 KB View Download