Also, crashlytics reports the same crash (affecting only chromebooks with android 7.1.1), but with this stack trace:

0  i965_dri.so                    0xce79a567 (Missing)
1  i965_dri.so                    0xce7d212c (Missing)
2  i965_dri.so                    0xce79a391 (Missing)
3  i965_dri.so                    0xcea534ae (Missing)
4  i965_dri.so                    0xce7a274c (Missing)
5  i965_dri.so                    0xcea534ae (Missing)
6  i965_dri.so                    0xce79a999 (Missing)
7  (Missing)                      0xf2b8ea30 (Missing)
8  libc.so                        0xf1e205d9 (Missing)
9  (Missing)                      0xf2b8ea20 (Missing)
10 libc.so                        0xf1e77f6e (Missing)
11 (Missing)                      0x12c8f768 (Missing)
12 libc.so                        0xf1e79400 (Missing)
13 libhwui.so                     0xf1066ec5 (Missing)
14 libandroid_runtime.so          0xedd8bf58 (Missing)
15 boot-framework.oat             0x7587dc3b (Missing)
16 libandroid_runtime.so          0xedd8bf46 (Missing)
17 (Missing)                      0x70efa870 (Missing)
18 boot-framework.oat             0x7585a63f (Missing)
19 (Missing)                      0x712d66bc (Missing)
20 (Missing)                      0x712cfe68 (Missing)
21 (Missing)                      0x70f66a50 (Missing)
22 boot-framework.oat             0x75506437 (Missing)
23 boot-framework.oat             0x7585d023 (Missing)
24 boot-framework.oat             0x7585d031 (Missing)
25 (Missing)                      0x712d04e0 (Missing)
26 libart.so                      0xed3b9508 (Missing)
27 (Missing)                      0x14c5c7e0 (Missing)
28 (Missing)                      0x7129eb14 (Missing)
29 (Missing)                      0x14c86270 (Missing)
30 boot-framework.oat             0x75882136 (Missing)
31 (Missing)                      0x7129eb14 (Missing)
32 (Missing)                      0x14c5c7e0 (Missing)
33 (Missing)                      0x76730920 (Missing)
34 (Missing)                      0x71097090 (Missing)
35 boot-framework.oat             0x75881ede (Missing)
36 (Missing)                      0x7129e8b0 (Missing)
37 (Missing)                      0x70f28778 (Missing)
38 boot-framework.oat             0x758800eb (Missing)
39 (Missing)                      0x7129eaa8 (Missing)
40 boot-framework.oat             0x7588292b (Missing)
41 (Missing)                      0x712d0fbc (Missing)
42 (Missing)                      0x135c6240 (Missing)
43 boot-framework.oat             0x75882c40 (Missing)
44 (Missing)                      0x14c86270 (Missing)
45 boot-framework.oat             0x758860bf (Missing)
46 (Missing)                      0x7129eb80 (Missing)
47 (Missing)                      0x14c86270 (Missing)
48 (Missing)                      0x14c63a80 (Missing)
49 (Missing)                      0x148e3c00 (Missing)
50 (Missing)                      0x148acc60 (Missing)
51 (Missing)                      0x7664d650 (Missing)
52 (Missing)                      0x14c7a9d0 (Missing)
53 (Missing)                      0x14c62ee0 (Missing)
54 boot-framework.oat             0x75882c40 (Missing)
55 libart.so                      0xed92ad7c (Missing)
56 (Missing)                      0x12c00060 (Missing)

Also, I am attaching crashlytics stats about the affected devices.

Deleted: crash_chromebook_devices.png 55.5 KB

	crash_chromebook_devices.png 55.5 KB View Download

This might not be the right channel to report issues with Android on Chrome OS, as I normally see those in our internal tracker. However, if you could tell us what application that is and how you reproduce the crash, someone from the graphics team may be able to check it. marcheu@, chadversary@, what do you think?

Note that this issue tracker is public, so if you think some of the information is sensitive, I'd recommend going with the internal path. Unfortunately I don't know how to do that, but let me add few more folks who may know.

The app is Bandlab, you can just download the latest version from Play Store:
https://play.google.com/store/apps/details?id=com.bandlab.bandlab

We have crash reports for versions of the app up to 7.7.2, which is currently the latest but will be replaced in a few days. The app has some native code, only for audio i/o and business logic, no native graphics rendering. I hope the breakpad microdump attached to this issue can somehow help, if you need we can also provide a debug build of our app.

Can we have any updates about this issue? We still have a lot of such crashes. We would happy to properly support Chromebooks, we believe our app is pretty useful on Chromebooks (this is musical editor) but looks that we have a lot of crashes on Chromebooks with ARC 7.1.
Maybe someone could forward this bug report to a proper issue tracker, we would happy to provide any required debug information that could help investigate this issue

+posciak for ARC++ platform
+Intel folks

If this is dying in the Intel driver we may need to bring in Intel, I am not sure how much we can get out of that form of crash dump.

We would happy to provide any required information, including debug builds of the app.
The problem that we don't have clear steps how to reproduce this, but it's possible even on debug builds

@bhthompson Can you add the Intel at Chromium entry to the CC list so we can have additional folks vectored in as well?  

@athos and other Bandlab folks on this thread.  

We tried (recording an audio track and changing the chrome book mode from tablet to Laptop and vice versa) on 
64-bit devices (Pixelbook and X2)
32-bit devices (Samsung Pro and Acer R11)
and the older version of the app where issue is reported (ver 7.7.2) and latest version of the app (ver 7.15.2), but couldn’t reproduce the issue. 

We did run into an ANR with the Acer R11 on R72 Dev that is not seen on an R11 on R70 Stable Channel.  But the ANR was not related to i965_dri.so.  


Bandlab folks: Above you mention you were able to duplicate a crash.  Do you have any info on how to reproduce that crash?  

Thanks

Hi everyone - this bug has gone dark. Can the submitter please verify the issue is still present? If so, please provide repro instructions OR data on failure rate? We're more than happy to look into it.

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.