New issue
Advanced search Search tips

Issue 874855 link

Starred by 1 user
Status: Closed
Owner:
bcwh...@chromium.org
Closed: Sep 6
Cc:
kkaluri@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Bus in base::PersistentMemoryAllocator::AllocateImpl

Project Member Reported by ClusterFuzz, Aug 16 
Detailed report: https://clusterfuzz.com/testcase?key=5155458437087232

Fuzzer: inferno_sampler
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: Bus
Crash Address: 0x7fcb2c476000
Crash State:
  base::PersistentMemoryAllocator::AllocateImpl
  base::PersistentMemoryAllocator::Allocate
  base::PersistentHistogramAllocator::AllocateHistogram
  
Sanitizer: address (ASAN)

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5155458437087232

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.

Comment 1 by kkaluri@chromium.org, Aug 17

Cc: kkaluri@chromium.org
Labels: M-69 Test-Predator-Wrong
Owner: bcwh...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "persistent_histogram_allocator.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/3f38b2253b19f9f9595f79fb92bfb5077e7b1959

bcwhite@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 2 by bcwh...@chromium.org, Sep 6

Status: Started (was: Assigned)

Comment 3 by bcwh...@chromium.org, Sep 6

Status: Closed (was: Started)
I ran the reproduction case...

/google/data/ro/teams/clusterfuzz-tools/releases/clusterfuzz reproduce 5155458437087232

... but don't get anything remotely the same.  Never a BUS error, anyway.  This was probably a transient failure during the original test rather than something that was reproducible.
Project Member

Comment 4 by ClusterFuzz, Sep 13

Labels: Needs-Feedback
ClusterFuzz testcase 5155458437087232 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
►

Sign in to add a comment