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

[GH-ISSUE #1946] SIGSEGV: segmentation violation when shutting down server with ctrl+c #1120

New Issue
Closed
opened 2026-04-12 10:52:00 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 10:52:00 -05:00
Owner
Copy Link

Originally created by @jmorganca on GitHub (Jan 12, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/1946

[GIN] 2024/01/12 - 12:38:39 | 200 |  5.985573917s |       127.0.0.1 | POST     "/api/chat"
2024/01/12 12:38:52 ext_server_common.go:158: loaded 0 images
^Cggml_metal_free: deallocating
SIGSEGV: segmentation violation
Originally created by @jmorganca on GitHub (Jan 12, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/1946 ``` [GIN] 2024/01/12 - 12:38:39 | 200 | 5.985573917s | 127.0.0.1 | POST "/api/chat" 2024/01/12 12:38:52 ext_server_common.go:158: loaded 0 images ^Cggml_metal_free: deallocating SIGSEGV: segmentation violation ```
GiteaMirror added the bug label 2026-04-12 10:52:00 -05:00
GiteaMirror commented 2026-04-12 10:52:00 -05:00
Author
Owner
Copy Link

@dcasota commented on GitHub (Jan 12, 2024):

As a volunteer feedback on this - after ollama-0.1.20, ext_server_common.go isn't part of the repo anymore, right? On an ollama make build with latest source I haven't seen a segmentation violation.

Btw. multiple llm servers using the same application instance would be on top of gpu driver capability. There are multi-instance gpu limitations, e.g. for nvidia in terms of driver mode (wddm/tcc) and its availability per gpu card. A baremetal prerequirement cascade might look like [cuda-capable gpu + baremetal, os version, cuda driver type and version, gcc version + correct development packages, application].

<!-- gh-comment-id:1889063231 --> @dcasota commented on GitHub (Jan 12, 2024): As a volunteer feedback on this - after ollama-0.1.20, ext_server_common.go isn't part of the repo anymore, right? On an ollama [make build](https://github.com/jmorganca/ollama/files/13918586/build_output.txt) with latest source I haven't seen a segmentation violation. Btw. multiple llm servers using the same application instance would be on top of gpu driver capability. There are multi-instance gpu limitations, e.g. for nvidia in terms of driver mode (wddm/tcc) and its availability per gpu card. A baremetal prerequirement cascade might look like [cuda-capable gpu + baremetal, os version, cuda driver type and version, gcc version + correct development packages, application].
GiteaMirror commented 2026-04-12 10:52:01 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Mar 12, 2024):

Pretty sure this has been resolved via llama.cpp bumps or other fixes we've done since early Jan. I get a clean shutdown on mac with the latest code.

<!-- gh-comment-id:1992274201 --> @dhiltgen commented on GitHub (Mar 12, 2024): Pretty sure this has been resolved via llama.cpp bumps or other fixes we've done since early Jan. I get a clean shutdown on mac with the latest code.
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#1120
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?