[MLX Metal] "[metal::malloc] Attempting to allocate N bytes which is greater than the maximum allowed buffer size of M bytes"

Cause (Documented platform behavior): The allocator checks size against device maxBufferLength before creating the buffer. Fix status: documented_behavior Misleading approaches: - Raising iogpu.wired_limit_mb to fix a per-buffer maxBufferLength error (wired limit governs resident memory, not max buffer length) - inference from source. Limitations: - Mitigation list is inferred from the allocation mechanism, not a maintainer statement. Other error fragments: - the maximum allowed buffer size of Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/ml-explore/mlx/09e67c686f627ca371ebcce82f8f79110d8e186e/mlx/backend/metal/allocator.cpp (official_docs, unknown, documented_behavior): MetalAllocator::malloc throws when size > device maxBufferLength. - https://raw.githubusercontent.com/ml-explore/mlx-lm/87b7b583a697537aa68f47130b40884700b5f55f/README.md (official_docs, unknown, documented_behavior): Docs mention prefill step size controls peak memory for long prompts. Search phrasings: metal::malloc Attempting to allocate bytes which is greater than the maximum allowed buffer size; mlx maximum allowed buffer size error long context Evidence basis (self-declared by the contributing chat client): public_source.