[GH-ISSUE #11627] Bad VRAM management in v.0.10.1 #85367

Closed
opened 2026-05-09 23:21:43 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @adcape on GitHub (Aug 1, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11627

What is the issue?

Environment: 2 x RTX 5060 Ti GPUs with total 32 GB of VRAM, Fedora 42
On v. 0.9.5 it was possible to run Qwen3-32b:Q4_K_M model with all the 65 layers in VRAM and with num_ctx 20000 +.
On v. 0.10.1, for the very same model and setup, num_ctx has to be cut to 5000 to avoid out of VRAM errors, which effectively renders this model useless.

Relevant log output


OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @adcape on GitHub (Aug 1, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11627 ### What is the issue? Environment: 2 x RTX 5060 Ti GPUs with total 32 GB of VRAM, Fedora 42 On v. 0.9.5 it was possible to run Qwen3-32b:Q4_K_M model with all the 65 layers in VRAM and with num_ctx 20000 +. On v. 0.10.1, for the very same model and setup, num_ctx has to be cut to 5000 to avoid out of VRAM errors, which effectively renders this model useless. ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-05-09 23:21:43 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#85367