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

[GH-ISSUE #14980] Memory layout cannot be allocated with num_gpu = N #9630

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

Originally created by @ioilmio on GitHub (Mar 20, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14980

What is the issue?

As per title i got this 500 error, memory layout cannot be allocated with num_gpu = N, where N is the number of GPU layer.
is this caused on how memory is managed by Ollama new update?
is downgrading an option?
thank you

Relevant log output

memory layout cannot be allocated with num_gpu = 26

OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

0.18.2

Originally created by @ioilmio on GitHub (Mar 20, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14980 ### What is the issue? As per title i got this 500 error, memory layout cannot be allocated with num_gpu = N, where N is the number of GPU layer. is this caused on how memory is managed by Ollama new update? is downgrading an option? thank you ### Relevant log output ```shell memory layout cannot be allocated with num_gpu = 26 ``` ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version 0.18.2
GiteaMirror added the bug label 2026-04-12 22:31:47 -05:00
GiteaMirror commented 2026-04-12 22:31:48 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 20, 2026):

Server logs will aid in debugging.

<!-- gh-comment-id:4099285040 --> @rick-github commented on GitHub (Mar 20, 2026): [Server logs](https://docs.ollama.com/troubleshooting) will aid in debugging.
GiteaMirror commented 2026-04-12 22:31:48 -05:00
Author
Owner
Copy Link

@ioilmio commented on GitHub (Mar 21, 2026):

The issue was ctx too large, env variables were not read correctly.
Sorry to bothered you.
Leave it here if someone face the same problem and wonder why.

<!-- gh-comment-id:4101649468 --> @ioilmio commented on GitHub (Mar 21, 2026): The issue was ctx too large, env variables were not read correctly. Sorry to bothered you. Leave it here if someone face the same problem and wonder why.
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#9630
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?