github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-22 05:31:43 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #13444] v0.13.3 creates gibberish output, but v0.13.2 doesn't #55388

New Issue
Closed
opened 2026-04-29 09:05:22 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-29 09:05:22 -05:00
Owner
Copy Link

Originally created by @zachrattner on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/13444

What is the issue?

In olllama v0.13.3 on my M4 Pro Mac mini, a simple question to Gemma gets gibberish output:

ollama --version
ollama version is 0.13.3

>> ollama run gemma3:12b-it-qat
>>> hi there tell me a joke
Okay, I have you_turn 
I can end_turn tell_a_ a_joke.turn.end_you_a joke? Iend"> tell_
turn

Why end_a_end 

<start_turn
Why did the turn_Why_
turn did the turn a joke_end chicken<start the end turn cross the turn the road?
<space end the_ turn to start road?end road?

<space
turn to the other<

end

<turn" >
To<To_ to get to the turn to space get to the_ end other side!turn"> other">
end

end</

 

<

<

I hope you start smile!end turn!
end_

<

< get it_turn"
turn_
-turn</p><end.

</ turn

turn_

</

<start>
</end>
Whyend>

But if I download v0.13.2 and run that, it all works ok:

>> ollama --version
ollama version is 0.13.2
>> ollama run gemma3:12b-it-qat
>>> hi there tell me a joke
Why don't scientists trust atoms? 

Because they make up everything! 😂

>>> Send a message (/? for help)

This problem is exacerbated by the setup where Ollama seems to automatically update itself, so you can't pin to a known working version. You just gotta disconnect the machine from the Internet or keep manually reinstalling the older version to keep the system working.

Relevant log output

See above.

OS

macOS

GPU

Apple

CPU

Apple

Ollama version

0.13.2

Originally created by @zachrattner on GitHub (Dec 12, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/13444 ### What is the issue? In olllama [v0.13.3](https://github.com/ollama/ollama/releases/tag/v0.13.3) on my M4 Pro Mac mini, a simple question to Gemma gets gibberish output: ``` ollama --version ollama version is 0.13.3 ``` ``` >> ollama run gemma3:12b-it-qat >>> hi there tell me a joke Okay, I have you_turn I can end_turn tell_a_ a_joke.turn.end_you_a joke? Iend"> tell_ turn Why end_a_end <start_turn Why did the turn_Why_ turn did the turn a joke_end chicken<start the end turn cross the turn the road? <space end the_ turn to start road?end road? <space turn to the other< end <turn" > To<To_ to get to the turn to space get to the_ end other side!turn"> other"> end end</ < < I hope you start smile!end turn! end_ < < get it_turn" turn_ -turn</p><end. </ turn turn_ </ <start> </end> Whyend> ``` But if I download [v0.13.2](https://github.com/ollama/ollama/releases/tag/v0.13.2) and run that, it all works ok: ``` >> ollama --version ollama version is 0.13.2 >> ollama run gemma3:12b-it-qat >>> hi there tell me a joke Why don't scientists trust atoms? Because they make up everything! 😂 >>> Send a message (/? for help) ``` This problem is exacerbated by the setup where Ollama seems to automatically update itself, so you can't pin to a known working version. You just gotta disconnect the machine from the Internet or keep manually reinstalling the older version to keep the system working. ### Relevant log output ```shell See above. ``` ### OS macOS ### GPU Apple ### CPU Apple ### Ollama version 0.13.2
GiteaMirror added the bug label 2026-04-29 09:05:22 -05:00
GiteaMirror commented 2026-04-29 09:05:25 -05:00
Author
Owner
Copy Link

@zachrattner commented on GitHub (Dec 12, 2025):

I reported this last night here: https://github.com/ollama/ollama/issues/12506#issuecomment-3644705389 but didn't have permission to reopen a closed ticket, so I am making a fresh one here

<!-- gh-comment-id:3648043125 --> @zachrattner commented on GitHub (Dec 12, 2025): I reported this last night here: https://github.com/ollama/ollama/issues/12506#issuecomment-3644705389 but didn't have permission to reopen a closed ticket, so I am making a fresh one here
GiteaMirror commented 2026-04-29 09:05:26 -05:00
Author
Owner
Copy Link

@Arman-Espiar commented on GitHub (Dec 12, 2025):

me too, I just updated to version 0.13.3 and encountered the same problem.

<!-- gh-comment-id:3648196429 --> @Arman-Espiar commented on GitHub (Dec 12, 2025): me too, I just updated to version 0.13.3 and encountered the same problem.
GiteaMirror commented 2026-04-29 09:05:26 -05:00
Author
Owner
Copy Link

@zachrattner commented on GitHub (Dec 12, 2025):

Nice! Thank you @jmorganca

<!-- gh-comment-id:3648199836 --> @zachrattner commented on GitHub (Dec 12, 2025): Nice! Thank you @jmorganca
GiteaMirror commented 2026-04-29 09:05:27 -05:00
Author
Owner
Copy Link

@ALIENvsROBOT commented on GitHub (Dec 12, 2025):

Image

Please fix it and release new version 🥲

<!-- gh-comment-id:3648285273 --> @ALIENvsROBOT commented on GitHub (Dec 12, 2025): <img width="1924" height="1127" alt="Image" src="https://github.com/user-attachments/assets/d807dfc2-05e3-48ad-ad8c-8d170d6d0d7d" /> Please fix it and release new version 🥲
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#55388
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?