github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 08:30:05 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #352] crash on allocated size greater than the recommended max working set size #154

New Issue
Closed
opened 2026-04-12 09:41:07 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 09:41:07 -05:00
Owner
Copy Link

Originally created by @BruceMacD on GitHub (Aug 15, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/352

When trying to load a large context window ollama crashed due to llama.cpp throwing an exception:

size =   160.00 MB, (12018.69 / 10922.67), warning: current allocated size is greater than the recommended max working set size
ggml_metal_graph_compute: command buffer 0 failed with status 5
GGML_ASSERT: ggml-metal.m:1177: false
SIGABRT: abort
PC=0x1a0f58724 m=10 sigcode=0
signal arrived during cgo execution

To reproduce:

  • download a 16K model
FROM llongma-2-7b.ggmlv3.q4_0.bin
PARAMETER num_ctx 16000
TEMPLATE """
{{ .Prompt }}
"""

Specs:
image

Originally created by @BruceMacD on GitHub (Aug 15, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/352 When trying to load a large context window ollama crashed due to llama.cpp throwing an exception: ``` size = 160.00 MB, (12018.69 / 10922.67), warning: current allocated size is greater than the recommended max working set size ggml_metal_graph_compute: command buffer 0 failed with status 5 GGML_ASSERT: ggml-metal.m:1177: false SIGABRT: abort PC=0x1a0f58724 m=10 sigcode=0 signal arrived during cgo execution ``` To reproduce: - download a 16K model ``` FROM llongma-2-7b.ggmlv3.q4_0.bin PARAMETER num_ctx 16000 TEMPLATE """ {{ .Prompt }} """ ``` Specs: <img width="277" alt="image" src="https://github.com/jmorganca/ollama/assets/5853428/f547523e-af64-46c6-9af0-82e81041d328">
GiteaMirror added the bug label 2026-04-12 09:41:07 -05:00
GiteaMirror commented 2026-04-12 09:41:08 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (Sep 7, 2023):

This should be fixed in https://github.com/jmorganca/ollama/releases/tag/v0.0.18 but feel free to re-open otherwise!

<!-- gh-comment-id:1710164766 --> @jmorganca commented on GitHub (Sep 7, 2023): This should be fixed in https://github.com/jmorganca/ollama/releases/tag/v0.0.18 but feel free to re-open otherwise!
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#154
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?