Abrt in base::subtle::PlatformSharedMemoryRegion::Create |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5936481072578560 Fuzzer: afl_hit_test_manager_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: Abrt Crash Address: 0x000000000001 Crash State: base::subtle::PlatformSharedMemoryRegion::Create base::subtle::PlatformSharedMemoryRegion::CreateWritable base::WritableSharedMemoryRegion::Create Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=552810:552819 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5936481072578560 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Apr 26 2018
Automatically adding ccs based on OWNERS file. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Apr 26 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/062ff1a58f51a17787de42e29d176f13658ef63a (Move Mojo internals to new base shared memory API). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Apr 26 2018
The log makes me suspicious that it could be an infra problem rather than a problem with my CL. This looks like an assertion failure within straightforward shared memory allocation. +inferno@ for clusterfuzz insight. Log: [0426/082720.084652:ERROR:platform_shared_memory_region_posix.cc(208)] Creating shared memory in /dev/shm/.org.chromium.Chromium.L9X1RQ failed: No such file or directory (2) [0426/082720.084859:ERROR:platform_shared_memory_region_posix.cc(211)] Unable to access(W_OK|X_OK) /dev/shm: No such file or directory (2) [0426/082720.084971:FATAL:platform_shared_memory_region_posix.cc(213)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix.
,
Apr 27 2018
,
Apr 27 2018
,
Apr 27 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/tools/clusterfuzz/+/ebd7ea940c2b85e97f2b7b52e14471ee1ee99fe2 commit ebd7ea940c2b85e97f2b7b52e14471ee1ee99fe2 Author: Oliver Chang <ochang@chromium.org> Date: Fri Apr 27 05:40:29 2018
,
Apr 27 2018
ClusterFuzz testcase 5936481072578560 appears to be flaky, updating reproducibility label.
,
Apr 27 2018
,
Oct 1
A crash was reported against chromium 69.0.3497.100 in Ubuntu 18.10 with a similar stacktrace top, but I can't access the details on clusterfuzz so I cannot be sure this is the same issue. See https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1795153 for details, including a stacktrace which I'm attaching here. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, Apr 26 2018Labels: Test-Predator-Auto-Components