Ollama unable to unload model if another program use (a little) VRAM

### What is the issue? ### Context I'm using Ollama on a dedicated VM with a L40S GPU (with paththrough). I'm using docker `docker run -d --gpus=all --restart always -e OLLAMA_DEBUG=1 -e OLLAMA_NUM_PARALLEL=1 -e OLLAMA_MAX_LOADED_MODELS=1 -v /:/root/.ollama -p 11434:11434 --name ollama ollama/ollama:latest` I have several users with different need and they load different models (from llama3.2 to deepseek-r1:70b). I have an Open-WebUI front-end on another machine that request ollama through the API. With one model at a time, it was working well. ### Description of the bug: Lately I wanted to add the possibility of image generation and installed comfyUI alongside ollama. (In its own container). I started to observe that each time comfyUI was running, ollama would start to freeze after some (random) time. Only killing ollama process or restarting the ollama container would make it back to work. I thought it was because comfyUI was taking too much VRAM but I was able to observe it even when it was just started (600 Mo VRAM) and with small models (llama3.2 is using 3Gb on my 48Gb VRAM available). I was able to narrow the problem : - loading the model is OK. - using the model is OK (several queries without any trouble) - unloading the model is the problem. Each time ollama try to unload the model (either to load another one or because timeout is reached), an ollama serve process launches and enter an infite loop (using 1 cpu at 100% forever). This behavior only occures if comfyUI use some VRAM. Without comfyUI, the unloading process goes well. That said, I think ollama should be able to unload models even if comfyUI is present, so I classify that as a bug. ### Visual exemple: 1/ Before running an ollama query (ollama docker is running but nothing in VRAM, comfyUI run but is idle, it use small chunk of VRAM)  2/ Running an ollama query (ollama load the model and return the answer. The…