Verified
Status Update
No update yet.
Comments
24...@project.gserviceaccount.com
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/6692d8fde6e787cf076f66795f49e8e221fadb1a (Translator: Remove deprecated window.translation
The window.translation API has been deprecated in favor of
window.ai.translator API.
Besides chrome/browser/policy/test/translator_api_policy_browsertest.cc,
this just removes code associated with window.translation.
translator_api_policy_browsertest.cc was missed when updating
browsertests to use window.ai.translator.
Fixed: 392185835
Change-Id: I3ef11db634a87fdd572cf57593bd0674b18afe8c
Reviewed-on:https://chromium-review.googlesource.com/c/chromium/src/+/6227852
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Ming-Ying Chung <mych@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Nathan Memmott <memmott@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1426365}
).
If this is incorrect, please let us know why and apply the hotlistid:5433122. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
The window.translation API has been deprecated in favor of
window.ai.translator API.
Besides chrome/browser/policy/test/translator_api_policy_browsertest.cc,
this just removes code associated with window.translation.
translator_api_policy_browsertest.cc was missed when updating
browsertests to use window.ai.translator.
Fixed: 392185835
Change-Id: I3ef11db634a87fdd572cf57593bd0674b18afe8c
Reviewed-on:
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Ming-Ying Chung <mych@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Nathan Memmott <memmott@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1426365}
).
If this is incorrect, please let us know why and apply the hotlistid:5433122. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
me...@google.com
me...@google.com
The check looks unrelated to the change I made. I couldn't reproduce this locally.
24...@project.gserviceaccount.com
ClusterFuzz testcase 5636848822976512 is verified as fixed in https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=1428966:1428976
If this is incorrect, please add the hotlistid:5433040 and re-open the issue.
If this is incorrect, please add the hotlistid:5433040 and re-open the issue.
Description
Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux
Crash Type: CHECK failure
Crash Address:
Crash State:
(connected_frame_count_ + 1) <= Page::MaxNumberOfFrames() in node_rare_data.cc
Sanitizer: undefined (UBSAN)
Regressed:
Reproducer Testcase:
Issue filed automatically.
To reproduce this, please build the target in this report and run it against the reproducer testcase. Please use the GN arguments provided at bottom of this report when building the binary.
If you have trouble reproducing, please also export the environment variables listed under "[Environment]" in the crash stacktrace.
If you have any feedback on reproducing test cases, let us know at