github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-16 13:19:40 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #15882] bug: 0.22.0 image generation working from DMG but not Homebrew with mlx response parse and mlx scanner errors #72180

New Issue
Open
opened 2026-05-05 03:35:54 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-05 03:35:54 -05:00
Owner
Copy Link

Originally created by @sean-freeman on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15882

What is the issue?

Ollama 0.22.0 image generation is working from DMG, but not when installation is performed using Homebrew.

May have some relation to https://github.com/ollama/ollama/issues/15107

Below log excerpt show errors only seen with Ollama 0.22.0 installed by Homebrew, tested using both models cited in experimental announcement in Jan-2026, x/z-image-turbo and x/flux2-klein. Command execution will accept and process, within 1-2 second reach 100% and stdout will show blank new line without any error message.

Test commands:

ollama run x/z-image-turbo "a cat"
ollama run x/flux2-klein "a cat"

Relevant log output

level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line=""
level=INFO source=server.go:128 msg=mlx-runner msg="    step 1: 0.00s (JIT warmup), peak 5.3 GB"
level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line=""
level=INFO source=server.go:128 msg=mlx-runner msg="    step 2: 0.00s, peak 5.3 GB"
level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line=""
level=INFO source=server.go:128 msg=mlx-runner msg="    step 3: 0.00s, peak 5.3 GB"
level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line=""
level=INFO source=server.go:128 msg=mlx-runner msg="    step 4: 0.00s, peak 5.3 GB"
level=INFO source=server.go:128 msg=mlx-runner msg="  Denoised 4 steps in 0.01s (0.00s/step), peak 5.3 GB"
level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line=""
level=WARN source=server.go:135 msg=mlx-runner msg="SIGSEGV: segmentation violation"
level=WARN source=server.go:135 msg=mlx-runner msg="PC=0x115423130 m=11 sigcode=2 addr=0x0"
level=WARN source=server.go:135 msg=mlx-runner msg="signal arrived during cgo execution"
....
....
....
level=WARN source=server.go:135 msg=mlx-runner msg="fault   0x0"
level=INFO source=server.go:128 msg=mlx-runner msg="  Decoding VAE... "
level=ERROR source=server.go:362 msg="mlx scanner error" error="unexpected EOF"

OS

macOS

GPU

Apple

CPU

Apple

Ollama version

0.22.0

Originally created by @sean-freeman on GitHub (Apr 29, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15882 ### What is the issue? Ollama 0.22.0 image generation is working from DMG, but not when installation is performed using Homebrew. May have some relation to https://github.com/ollama/ollama/issues/15107 Below log excerpt show errors only seen with Ollama 0.22.0 installed by Homebrew, tested using both models cited in experimental announcement in Jan-2026, `x/z-image-turbo` and `x/flux2-klein`. Command execution will accept and process, within 1-2 second reach 100% and stdout will show blank new line without any error message. Test commands: ``` ollama run x/z-image-turbo "a cat" ollama run x/flux2-klein "a cat" ``` ### Relevant log output ```shell level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=INFO source=server.go:128 msg=mlx-runner msg=" step 1: 0.00s (JIT warmup), peak 5.3 GB" level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=INFO source=server.go:128 msg=mlx-runner msg=" step 2: 0.00s, peak 5.3 GB" level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=INFO source=server.go:128 msg=mlx-runner msg=" step 3: 0.00s, peak 5.3 GB" level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=INFO source=server.go:128 msg=mlx-runner msg=" step 4: 0.00s, peak 5.3 GB" level=INFO source=server.go:128 msg=mlx-runner msg=" Denoised 4 steps in 0.01s (0.00s/step), peak 5.3 GB" level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=WARN source=server.go:135 msg=mlx-runner msg="SIGSEGV: segmentation violation" level=WARN source=server.go:135 msg=mlx-runner msg="PC=0x115423130 m=11 sigcode=2 addr=0x0" level=WARN source=server.go:135 msg=mlx-runner msg="signal arrived during cgo execution" .... .... .... level=WARN source=server.go:135 msg=mlx-runner msg="fault 0x0" level=INFO source=server.go:128 msg=mlx-runner msg=" Decoding VAE... " level=ERROR source=server.go:362 msg="mlx scanner error" error="unexpected EOF" ``` ### OS macOS ### GPU Apple ### CPU Apple ### Ollama version 0.22.0
GiteaMirror added the bug label 2026-05-05 03:35:54 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#72180
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?