pitrou opened a new issue, #45011: URL: https://github.com/apache/arrow/issues/45011
### Describe the bug, including details regarding any error messages, version, and platform. This failure should be investigated as it may point to a bogus memory allocation somewhere in Arrow: https://github.com/ursacomputing/crossbow/actions/runs/12294007130/job/34307892977#step:7:5867 The "alignment: 4194304" note is a bit fishy. ``` ----------------------------- Captured stderr call ----------------------------- mimalloc: warning: unable to allocate aligned OS memory directly, fall back to over-allocation (4194304 bytes, address: 0xea6b2000, alignment: 4194304, commit: 1) mimalloc: warning: mi_usable_size: pointer might not point to a valid heap region: 0xea408080 (this may still be a valid very large allocation (over 64MiB)) mimalloc: warning: (yes, the previous pointer 0xea408080 was valid after all) mimalloc: warning: mi_usable_size: pointer might not point to a valid heap region: 0xea408080 (this may still be a valid very large allocation (over 64MiB)) mimalloc: warning: (yes, the previous pointer 0xea408080 was valid after all) mimalloc: warning: mi_free: pointer might not point to a valid heap region: 0xea408080 (this may still be a valid very large allocation (over 64MiB)) mimalloc: warning: (yes, the previous pointer 0xea408080 was valid after all) ``` ### Component(s) Continuous Integration, Python -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
