Two distinct glibc heap-consistency failures were observed in an
out-of-pipeline concurrency diagnostic. The second is localized to the
producer thread and the jpeg-decode -> calloc -> _int_malloc -> sysmalloc
path; the corrupting writer is not identified and the two failures are not
shown to share a root cause. No fix and no concurrency-stability claim.
Static checks found no contract violation within the covered scope only.