Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 1223031]
UI>Accessibility
Supplemental component tags only. Set main component first. [ID: 1222907]
[ID: 1223136]
Design doc to be reviewed. [ID: 1223032]
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
[ID: 1223084]
[ID: 1223086]
[ID: 1223034]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
[ID: 1223088]
This field contains Gerrit urls of code changes that ‘fix’ a security bug (i.e., excluding logging/cleanup commits) and is used when a singular fix cannot be uniquely identified from the existing “Code Changes” field. The change can be in the chromium repo or any other third_party repo. [ID: 1358989]
UI
[ID: 1253656]
View issue level access limits(Press Alt + Right arrow for more information)
Estimated effort
Unintended behavior
View staffing
Description
I have a local ToT Android build 3ae65a4fcccddfe3d353f332f26f66639f167f62 which is hitting `DUMP_WILL_BE_CHECK(wrapper);` when running MotionMark 1.2:
gn args
```
target_os = "android"
target_cpu = "arm64"
use_remoteexec=true
is_debug = false
dcheck_always_on=true
```
I was not interacting with the device at the time, one of the stories was running, I forget which one. I hadn't turned on any a11y features.