GH-47588: [C++] Bump mimalloc version to 3.1.5

[pitrou]

Rationale for this change

According to microsoft/mimalloc#1073 , mimalloc v3 is preferred over v2 for production usage.

There are reports of higher than expected memory consumption with mimalloc 2.2.x, notably when reading Parquet data (example: GH-47266).

What changes are included in this PR?

Bump to mimalloc 3.1.5, which is the latest mimalloc 3.1.x release as of this writing.

Are these changes tested?

Yes, by existing tests and CI.

Are there any user-facing changes?

Hopefully not, besides a potential reduction in memory usage due to improvements in mimalloc v3.

• GitHub Issue: [C++] Bump mimalloc version #47588

[pitrou]

@github-actions crossbow submit -g cpp

[pitrou]

@github-actions crossbow submit -g cpp

[pitrou]

@github-actions crossbow submit -g cpp

[pitrou]

@ursabot please benchmark

[voltrondatabot]

Benchmark runs are scheduled for commit 709942b35328dbf4c84206bfc8fc6c0071448639. Watch https://buildkite.com/apache-arrow and https://conbench.ursa.dev for updates. A comment will be posted here when the runs are complete.

[conbench-apache-arrow]

Thanks for your patience. Conbench analyzed the 4 benchmarking runs that have been run so far on PR commit 709942b35328dbf4c84206bfc8fc6c0071448639.

There were 80 benchmark results indicating a performance regression:

• Pull Request Run on amd64-c6a-4xlarge-linux at 2025-09-18 15:51:49Z
  • CopyBitmapWithoutOffset (C++) with params=8192, source=cpp-micro, suite=arrow-bit-util-benchmark
  • ReadUncachedFile (C++) with params=num_cols:64/is_partial:1/real_time, source=cpp-micro, suite=arrow-ipc-read-write-benchmark
• and 78 more (see the report linked below)

The full Conbench report has more details.

[pitrou]

@github-actions crossbow submit -g cpp

[pitrou]

@github-actions crossbow submit -g cpp

[pitrou]

CI failures are unrelated. Should we merge this @kou@WillAyd ?

[kou]

+1

[pitrou]

@github-actions crossbow submit -g cpp -g r cp313

[github-actions]

Revision: 4294e34

Submitted crossbow builds: ursacomputing/crossbow @ actions-562e16c367

Task	Status
example-cpp-minimal-build-static
example-cpp-minimal-build-static-system-dependency
example-cpp-tutorial
r-binary-packages
r-recheck-most
test-build-cpp-fuzz
test-conda-cpp
test-conda-cpp-valgrind
test-cuda-cpp-ubuntu-22.04-cuda-11.7.1
test-debian-12-cpp-amd64
test-debian-12-cpp-i386
test-fedora-42-cpp
test-r-arrow-backwards-compatibility
test-r-depsource-bundled
test-r-depsource-system
test-r-dev-duckdb
test-r-devdocs
test-r-extra-packages
test-r-gcc-11
test-r-gcc-12
test-r-install-local
test-r-install-local-minsizerel
test-r-linux-as-cran
test-r-linux-rchk
test-r-linux-sanitizers
test-r-linux-valgrind
test-r-m1-san
test-r-macos-as-cran
test-r-minimal-build
test-r-offline-maximal
test-r-offline-minimal
test-r-rhub-debian-gcc-devel-lto-latest
test-r-rhub-ubuntu-gcc12-custom-ccache
test-r-rhub-ubuntu-release-latest
test-r-rocker-r-ver-latest
test-r-rstudio-r-base-4.1-focal
test-r-rstudio-r-base-4.2-focal
test-r-ubuntu-22.04
test-r-versions
test-ubuntu-22.04-cpp
test-ubuntu-22.04-cpp-20
test-ubuntu-22.04-cpp-bundled
test-ubuntu-22.04-cpp-emscripten
test-ubuntu-22.04-cpp-no-threading
test-ubuntu-24.04-cpp
test-ubuntu-24.04-cpp-bundled-offline
test-ubuntu-24.04-cpp-gcc-13-bundled
test-ubuntu-24.04-cpp-gcc-14
test-ubuntu-24.04-cpp-minimal-with-formats
test-ubuntu-24.04-cpp-thread-sanitizer
wheel-macos-monterey-cp313-cp313-amd64
wheel-macos-monterey-cp313-cp313-arm64
wheel-macos-monterey-cp313-cp313t-amd64
wheel-macos-monterey-cp313-cp313t-arm64
wheel-manylinux-2-28-cp313-cp313-amd64
wheel-manylinux-2-28-cp313-cp313-arm64
wheel-manylinux-2-28-cp313-cp313t-amd64
wheel-manylinux-2-28-cp313-cp313t-arm64
wheel-musllinux-1-2-cp313-cp313-amd64
wheel-musllinux-1-2-cp313-cp313-arm64
wheel-musllinux-1-2-cp313-cp313t-amd64
wheel-musllinux-1-2-cp313-cp313t-arm64
wheel-windows-cp313-cp313-amd64
wheel-windows-cp313-cp313t-amd64

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit e1f727c.

There were 5 benchmark results indicating a performance regression:

• Commit Run on amd64-m5-4xlarge-linux at 2025-10-09 10:35:17Z
  • csv-read (Python) with compression=gzip, dataset=nyctaxi_2010-01, output_format=arrow_table, streaming=streaming
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-21, scale_factor=10
• and 3 more (see the report linked below)

The full Conbench report has more details. It also includes information about 16 possible false positives for unstable benchmarks that are known to sometimes produce them.

[lesterfan]

Are there any user-facing changes?
Hopefully not, besides a potential reduction in memory usage due to improvements in mimalloc v3.

Just wanted to note that this change actually fixes an issue we've been observing with libarrow.so and the address sanitizer! Here is the issue I just filed for reference: #47828.