Issue metadata
Sign in to add a comment
|
Crash in libpulsecommon-4.0.so |
||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6013750452944896 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: UNKNOWN Crash Address: 0x9e0ff004 Crash State: libpulsecommon-4.0.so Recommended Security Severity: Medium Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96_jB1xBe4lkJMkE4mq1KGHDlTf7H1p2urpg8MiFY1XFkNOnHTDQR0p53hZQsmWAAqY67pO7kOH4LSB5GOeusObNM7lZTdtr1naFZHo0j-twzXpdj0spjRULQnDbLCcKSrysV-IQhXQYVbr2WUJGbnGOGEQfh0M871MyxXogRDQYQF4kL4?testcase_id=6013750452944896 Filer: tanin See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 21 2016
Hmm, I'm not sure what I can do with this. It's a crash in a system library with no trace information. It's arm + pulse too, which we have no shipping users of AFAIK.
,
Jun 21 2016
(ChromeOS uses CrAS instead of Pulse and Android use OpenSLES instead of Pulse)
,
Jun 21 2016
Dale, any setup instructions you can give us so that on our bots, we can switch chrome to using CrAS instead of libpulse ?
,
Jun 21 2016
Are you building chromeos=1 ? issue 621129 has some details from someone who recently tried building this path.
,
Jun 21 2016
We have both chromeos=1 asan buildbot and regular one without it. So, we need to use "use_cras" on regular buildbot without needing chromeos=1
,
Jun 21 2016
Since there's no reproducible testcase (despite CF marking it as so at first), I'm going to mark this as WontFix, although it's still possible that some pulseaudio backend change could've caused this right? It seems hard to track down when this started happening though, we've been seeing this for a few months. (The "arm" in the job type doesn't actually mean this is Chrome on ARM, it refers to the v8 arm simulator).
,
Jun 21 2016
,
Jun 22 2016
This crash shows up again today. https://cluster-fuzz.appspot.com/testcase?key=5989409598210048
,
Sep 13 2016
Issue 646206 has been merged into this issue.
,
Sep 13 2016
Issue 646408 has been merged into this issue.
,
Sep 13 2016
,
Sep 28 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 1 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 2 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 2 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ta...@google.com
, Jun 21 2016