commit | a58bd6d042ccb5be5d196bd546ba1b1039fdb080 | [log] [tgz] |
---|---|---|
author | Etienne Bergeron <etienneb@chromium.org> | Mon May 26 21:14:37 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 26 21:14:37 2025 |
tree | 154c2513fd6453946c06e2159fa7d2ed4df82e02 | |
parent | 046f6798f268669593f7d12c1ff41457a979b7e5 [diff] |
Fix a crash due do retrieving diagnostic after database open failed. This CL is fixing an crash caused by a databased not being opened while requesting diagnostic information. The error goes like this: * OpenDatabase - sqlite_open failed - db_ is not set, and stays null - error_calback is called * HistoryBackend request the diagnostic error - sql::Database::GetDiagnosticInfo - sql::Database::Execute And the function sql::Database::Execute has a DCHECK that enforce the db_ to not be null or to be poisoned. see: https://source.chromium.org/chromium/chromium/src/+/main:sql/database.cc;l=1522;drc=a6f95e740f15dc909935fee1c41c77aeefdaa727 Test: Running the test without the fix does crash. Bug: 420369590 Change-Id: I60b5af1d0a504c7bffd61aadb977d9aac1158a78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6586533 Reviewed-by: Sophie Chang <sophiechang@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/main@{#1465663}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.