Issue metadata
Sign in to add a comment
|
Chrome Canary 72 mostly wipes IndexedDB data values
Reported by
stefan.s...@googlemail.com,
Oct 28
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Use Canary browser and upgrade to version 72 2. IndexedDB is wiped 3. What is the expected behavior? IndexedDB should be successfully migrated What went wrong? Most values in IndexedDB are set to null. Some however seem to have survived. Indices are not affected. Did this work before? Yes ? Does this work in other browsers? Yes Chrome version: 72.0.3593.0 Channel: canary OS Version: OS X 10.13.6 Flash Version: If this makes it into stable its a disaster.
,
Oct 29
,
Oct 29
Thanks for filing the issue! This issue looks to have a same root cause as issue: 899446 , hence as per bisect info provided in comment# 2 in issue: 899446 , assigning it to respective Dev. Change Log: https://chromium.googlesource.com/chromium/src/+/d42a4b6fc73f5de8851ee0ee6f64876a5e3efb03 Change-Id: I85fa493b345bb6ab955316fe1725e4794ed4c99b Reviewed-on: https://chromium-review.googlesource.com/c/1265900 @Chase Phillips: Please confirm the issue and help in re-assigning if it is not related to your change. Adding ReleaseBlock-Stable for M-72, feel free to remove it if not applicable. Thanks!
,
Oct 30
Thanks for the report! From what I can tell this is the same root cause as issue 899446 . I'll be posting an update there so marking this as a duplicate of that issue. Thanks again. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Oct 29