Steps to reproduce the problem:
1. Enable Breakpad in a local dev build.
2. Visit chrome://crash
3. Crash generation fails with a "Crash dump generation failed." message from breakpad.

What is the expected behavior?
The report should have been generated properly and stored on the device (usually in /data/data/Cache/Crash Reports/).

What went wrong?
It looks like SELinux blocked the process from creating and writing to a temp file. (setenforce 0 fixes this).

avc: denied { open } for name=".org.chromium.Chromium.bUTYFj" dev="dm-1" ino=409662 scontext=u:r:isolated_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=file permissive=0

This only happens on my Nexus 6 and Nexus 6p (Both running 6.0.1). I've also tried this on a Nexus 5 also running the same release and it worked just fine. Why would the rules be different on the same Android version (probably not the right place for that question).

Am I doing anything wrong here? Is this expected behavior?

Did this work before? Yes Prior to Android 6.0

Chrome version: 46.0.2490.385  Channel: dev
OS Version: 6.0.1
Flash Version: 

Might not be a Chromium Issue, but I thought I should report it.