Assigned
Status Update
Comments
sa...@google.com <sa...@google.com> #2
Thanks for reporting and sample repro
Reproducible on chrome stable #134.0.6998.47(OS:Mac 15.3, Linux and Windows 11)
Crash id -https://crash.corp.google.com/browse?q=reportid=%2747f432dbf0fd86d5%27
Reproducible on chrome channels:
134.0.6998.23 -beta
135.0.7023.0 -dev
135.0.7041.2-canary
bisect info:
131.0.6778.0-Bad
131.0.6777.0-Good
script:python3 bisect_builds.py -o -a mac -g 131.0.6777.0 -b 131.0.6778.0 -- --no-first-run
CHANGELOG URL:
You are probably looking for a change made after 1368505 (known good), but no later than 1368506 (first known bad).
https://chromium.googlesource.com/chromium/src/+log/687ad1c377870eadcf593ccc90ec728de6d7baf3..3952cce4d0a027ebb349a094ebe1859aee54f463
Change-Id: Id154ef0f5882f268d40a60d4b6c54dd6260be591
Reviewed-on:https://chromium-review.googlesource.com/c/chromium/src/+/5771755
japhet@Could you please take a look if this is related to your change. Thanks!
Reproducible on chrome stable #134.0.6998.47(OS:Mac 15.3, Linux and Windows 11)
Crash id -
Reproducible on chrome channels:
134.0.6998.23 -beta
135.0.7023.0 -dev
135.0.7041.2-canary
bisect info:
131.0.6778.0-Bad
131.0.6777.0-Good
script:python3 bisect_builds.py -o -a mac -g 131.0.6777.0 -b 131.0.6778.0 -- --no-first-run
CHANGELOG URL:
You are probably looking for a change made after 1368505 (known good), but no later than 1368506 (first known bad).
Change-Id: Id154ef0f5882f268d40a60d4b6c54dd6260be591
Reviewed-on:
japhet@Could you please take a look if this is related to your change. Thanks!
Description
Steps to reproduce the problem
Problem Description
This crash happens since chrome 132, it is a regression (Windows, Linux and MacOS). The crash happens when Lit-html library render the page. For an other project we reimplement it without Lit-html library and we resolve the issue.
Note: we are dedicating this data purged server for this Chrome bug, please let us know when we can reuse it and delete this "testBugChrome" account.
Additional Comments
We have consistently reproduced this bug on over 20 different devices.
Summary
Since Chrome 132, random crash with STATUS_ACCESS_VIOLATION in a Lit-html render page
Additional Data
Category: JavaScript
Chrome Channel: Dev
Regression: Yes