since chrome 61 version, there're delay while loading new webview from another
Reported by
lik...@gmail.com,
Nov 8 2017
|
|||||
Issue descriptionTHIS TEMPLATE IS FOR FILING BUGS ON THE ANDROID SYSTEM WEBVIEW. GENERAL WEB BUGS SHOULD BE FILED USING A DIFFERENT TEMPLATE! Device name: all devices Android version: both of 7 and 8 WebView version (from system settings -> Apps -> Android System WebView): chrome web view (we can find this issue since version 61) Application: Application version: some application using webview URLs (if applicable): Steps to reproduce: (1) one a webview on activity (2) handle some click event to load new url on the other webview activy (3) it cause 5 ~ 7 seconds loading delay Expected result: load page without delay Actual result: since chrom version 61, there're 5~7 seconds loading delay at that time we can see the logs... 11-07 10:13:28.893 E/chromium(21359): [ERROR:connection.cc(1947)] Web sqlite error 5, errno 0: database is locked, sql: PRAGMA auto_vacuum 11-07 10:13:28.895 E/chromium(21359): [ERROR:connection.cc(1947)] Web sqlite error 5, errno 0: database is locked, sql: PRAGMA journal_mode = TRUNCATE 11-07 10:13:29.900 E/chromium(21359): [ERROR:connection.cc(1947)] Web sqlite error 5, errno 0: database is locked, sql: PRAGMA cache_size=32 11-07 10:13:29.900 E/chromium(21359): [ERROR:connection.cc(1947)] Web sqlite error 5, errno 0: database is locked, sql: SELECT name FROM sqlite_master WHERE type=? AND name=? COLLATE NOCASE 11-07 10:13:29.901 E/chromium(21359): [ERROR:connection.cc(1947)] Web sqlite error 5, errno 0: database is locked, sql: SELECT name FROM sqlite_master WHERE type=? AND name=? COLLATE NOCASE 11-07 10:13:29.901 E/chromium(21359): [ERROR:connection.cc(1947)] Web sqlite error 5, errno 0: database is locked, sql: SELECT COUNT(*) FROM sqlite_master 11-07 10:13:29.901 E/chromium(21359): [ERROR:connection.cc(1947)] Web sqlite error 5, errno 0: database is locked, sql: SELECT name FROM sqlite_master WHERE type=? AND name=? COLLATE NOCASE 11-07 10:13:29.901 E/chromium(21359): [ERROR:connection.cc(1947)] Web sqlite error 5, errno 0: database is locked, sql: CREATE TABLE meta(key LONGVARCHAR NOT NULL UNIQUE PRIMARY KEY, value LONGVARCHAR) 11-07 10:13:29.902 E/chromium(21359): [ERROR:web_database_backend.cc(113)] Cannot initialize the web database: 1 11-07 10:13:29.918 D/ContextRelationMgrBrdg(21518): loadKlass() : caller=com.samsung.android.bridge.multiscreen.common.ContextRelationManagerBridge.<clinit>:28 android.app.LoadedApk.makeApplication:840 11-07 10:13:29.926 W/chromium(21359): [WARNING:aw_form_database_service.cc(24)] initializing autocomplete database failed
,
Nov 9 2017
Then... I wonder why previous version of chrome 61 does not affect this issue. Is there any changes on policy or something?
,
Nov 9 2017
Thank you for providing more feedback. Adding requester "torne@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 9 2017
It was never safe to do this; it can cause random crashes or data loss, and we explicitly warn about this in logcat at startup telling you not to do it if we detect it (this was added a long time ago). If that's what's happening here, then something has happened to change the database handling inside chromium, and we aren't going to fix that because it's not a bug - this has never actually "worked". It's only luck that it doesn't crash :) Is that actually what's happening in your app, though? Are the two activities you mentioned running in different processes? Do you see the warning in logcat telling you that this is unsafe?
,
Dec 5 2017
@liky95 -- Could you please respond to Comment# 4 and provide an update for the issue so that it would help us to triage further. Thanks in Advance.
,
Jan 9 2018
Closing this issue as WontFix, due to lack of response from reporter. @liky95: Please feel free to log a new issue if you face any. Thanks!! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by torne@chromium.org
, Nov 8 2017