Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[linux/wayland] Introduced a workaround for the crash. [merge to M103]
In recent versions we have got a crash (see the linked crbug) that is unclear how to investigate. The code has DCHECKs but apparently users who report crashes do not have means to diagnose the issue. This patch adds a workaround (early return of the default) so that the browser should fall back to the default path in the situation that caused the crash. (cherry picked from commit 09ccc58) Bug: 1323635 Change-Id: I1f8a0bc79cf866d9f3405c21c7c0e5b868a55bf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3657308 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by: Maksim Sisov <msisov@igalia.com> Auto-Submit: Alexander Dunaev <adunaev@igalia.com> Commit-Queue: Alexander Dunaev <adunaev@igalia.com> Cr-Original-Commit-Position: refs/heads/main@{#1005731} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3660303 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5060@{#172} Cr-Branched-From: b83393d-refs/heads/main@{#1002911}
- Loading branch information