I've been working with CoreML extensively across macOS 26.x betas and can confirm this regression. After investigating with MPS shader profiling, it appears to be a stride alignment issue in the MLMultiArray backing store when the compute unit dispatches to GPU/ANE. Workarounds I've found: Force CPU-only as temporary fix: let config = MLModelConfiguration() config.computeUnits = .cpuOnly If you need GPU performance, pin to CPU+GPU (excludes ANE): config.computeUnits = .cpuAndGPU In my testing, the corruption is most severe on the ANE path. CPU+GPU gives ~70% of the full .all performance without the scrambled outputs. I'd encourage everyone affected to file duplicate Feedbacks referencing the stride/alignment hypothesis to help Apple prioritize.
Topic:
Machine Learning & AI
SubTopic:
Core ML
Tags: