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

[GH-ISSUE #1362] ollama at startup causing kernel_task to run all times on macos #62751

New Issue
Closed
opened 2026-05-03 10:10:52 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-03 10:10:52 -05:00
Owner
Copy Link

Originally created by @ogulcancelik on GitHub (Dec 3, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/1362

I don't have a proper log, or data to share but I wanted to post this anyway.

I am using M2 Max and installed ollama, it automatically starts as a login item. I realized my idle temps were 80C and also kernel_task was eating a lot of CPU time. It was fixed as soon as I removed ollama from login items. Closing it didn't fix it, so my guess is, as soon as it starts as a login item, it creates a ghost process that macos continuously tries to close, hence, creating high process uptime on kernal_task and high temps.

I'm sorry that I can't provide more detail as I removed ollama completely, but wanted to open this issue for future reference, if someone has the same problem.

Originally created by @ogulcancelik on GitHub (Dec 3, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1362 I don't have a proper log, or data to share but I wanted to post this anyway. I am using M2 Max and installed ollama, it automatically starts as a login item. I realized my idle temps were 80C and also `kernel_task` was eating a lot of CPU time. It was fixed as soon as I removed ollama from login items. Closing it didn't fix it, so my guess is, as soon as it starts as a login item, it creates a ghost process that macos continuously tries to close, hence, creating high process uptime on kernal_task and high temps. I'm sorry that I can't provide more detail as I removed ollama completely, but wanted to open this issue for future reference, if someone has the same problem.
GiteaMirror commented 2026-05-03 10:10:54 -05:00
Author
Owner
Copy Link

@ogulcancelik commented on GitHub (Dec 3, 2023):

I realized this is not ollama but chatgpt on chrome ffs:
https://community.openai.com/t/high-cpu-web-workers-usage-of-chatgpt-when-not-is-use/230447

<!-- gh-comment-id:1837547983 --> @ogulcancelik commented on GitHub (Dec 3, 2023): I realized this is not ollama but chatgpt on chrome ffs: https://community.openai.com/t/high-cpu-web-workers-usage-of-chatgpt-when-not-is-use/230447
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
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#62751
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?