bcwhite@: This is an ASAN crash showing in PersistentHistogramAllocator, are you able to investigate?

Is this reproducable?  I'm running it on my workstation according to the instructions given (I'm new to this), including increasing it to 2500 runs.  No crashes.

I'm not entirely sure I have a correct environment, though.  It says it cannot find some processes but I've installed those packages:

Xvfb: no process found
blackbox: no process found
blackbox: managing screen 0 using TrueColor visual 0x21, depth 24
/etc/X11/blackbox/blackbox-menu: No such file or directory
/home/bcwhite/tmp/asan-linux-release-422171/chrome --user-data-dir=/tmp/tmpQfFFMV/temp/user_profile_0 --log-net-log=/tmp/tmpQfFFMV/temp/net_log_0 --js-flags="--expose-gc --verify-heap" --no-first-run --use-gl=osmesa /home/bcwhite/clusterfuzz/slave-bot/inputs/fuzzer-testcases/fuzz-peach-JPG-230.JPG
Starting run number: 0
Starting run number: 1
Starting run number: 2
Starting run number: 3
Starting run number: 4
Starting run number: 5
Starting run number: 6
Starting run number: 7
Starting run number: 8
Starting run number: 9
Starting run number: 10
Starting run number: 11
Starting run number: 12
Starting run number: 13
Starting run number: 14
Starting run number: 15
Starting run number: 16
Starting run number: 17
Starting run number: 18
Starting run number: 19
Starting run number: 20
Starting run number: 21
Starting run number: 22
Starting run number: 23
Starting run number: 24
No crash found.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
      after 444 requests (444 known processed) with 0 events remaining.
blackbox: no process found

This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is completely within the control of a Finch experiment so shouldn't block anything.

Could use some help reproducing it, though.

I'm pretty sure that no code changes are responsible for this but rather the CL that enabled testing with the PersistentHistograms feature enabled.

Trying to reproduce it locally.

This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

**** Bulk edit -  please ignore if not applicable ****

This bug  is reported as M55 Beta blocker and we're getting closer to M55 Beta promotion. 
Please plan to have fix ready and merged to M55 branch (2883) by 5:00 PM PT, Monday(10/10) so it has enough baking time in Dev before Beta promotion. Thank you.

I'm unable to produce this on my (Ubuntu) Linux workstation or (Goobuntu) Ubiquity.  It never crashes with the provided build or my own build.  I've used command-line flags and even code changes to ensure that PersistentHistograms are enabled.  Never a crash.

Is it possible that it was a different thread that did the SEGV?

The line in my code that is identified shouldn't cause a crash.  It's a pointer but it's been verified as valid in preceding code so I don't see how it could be out-of-bounds.

If I'm going to investigate further, I'm going to need a way to reproduce it locally or at least get a core dump that I can load into gdb.

If it is assuredly my code causing the crash, the beta-blocker label can be removed since histogram persistence is controlled by an experiment.  I did that once but sheriffbot put it back.

Thanks for digging into this bcwhite@.  mbarbella@, any suggestions?  (Adding ReleaseBlock-NA to stop sheriffbot putting the label back.)

mbarbella, any ideas?

This seems no longer reproducible on CF, and we're not seeing any new instances of it. WontFixing.

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