Search Issue Tracker

Fixed

Fixed in 2021.3.14f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a17

Votes

1

Found in

2021.3.12f1

2022.1.0b11

2022.2.0a9

2023.1.0a9

Issue ID

UUM-781

Regression

No

[ChromeOS] Only a few frames are reported in logcat's stack trace when using x86_64 or ARMv7 architectures on Pixelbook

--

-

Steps to reproduce:

1. Open attached project
2. Make sure the architecture is set to x86_64 or ARMv7
3. Build and run on ChromeOS device, that supports ChromeOS architectures
4. When in application, press "Crash with Utils - Access Violation"
5. Observe the stack trace in logcat

Expected: a larger amount (15-40) frames reported
Actual: 2 frames reported

Reproduced in: 2021.2.15f1, 2022.1.0b11, 2022.2.0a9

Devices that reproduce the issue:
VLNQA00425 - Google Pixelbook (Google Pixelbook), CPU: -, GPU: virgl (Mesa DRI Intel(R) HD Graphics 615 (KBL GT2)), OS: 11 (arcvm enabled)

Devices that do not reproduce the issue:
VLNQA00433 - Lenovo Chromebook Duet (kukui), CPU: -, GPU: Mali-G72, OS: 9. (intel-only device, therefore only tested on ARMv7)

Note: happens in release/developer mode
Note3: logcat is attached (ChromeOSstackTrace.txt)
Note4: comparison with other architectures:
• ARMv7 2 frames
• ARM64 18 frames
• x86 25 frames
• x86-64 2 frames

Add comment

Log in to post comment