Problemsby IbisChroma GPU access and drivers are painful
MLOps2 posts from 1 person1d active+22 posts in the last 7 days, 0 the 7 days before (new)Unverified
Posts per day
The posts behind it
2, newest first[Bug]: HTTP clients leave an unreleasable entry in SharedSystemClient._identifier_to_system after close() (orphan from _populate_data_from_system)### What happened? For HTTP-backed clients the system identifier is a fresh `uuid4()` on every call to `SharedSystemClient._get_identifier_from_settings`. `Client.__init__` creates the internal admin client with `AdminClient.from_system(self._system)`, which calls...chroma-core/chroma · JIAQIAOpen ↗[Bug]: AsyncFastAPI keeps one httpx.AsyncClient per event loop forever; System.stop() cleanup is skipped inside a running loop### What happened? `AsyncFastAPI._clients` is a class-level `Dict[int, httpx.AsyncClient]` keyed by `hash(asyncio.get_event_loop())`. A new `httpx.AsyncClient` is added for every event loop that ever makes a request, and nothing removes it when that loop closes. In a process...chroma-core/chroma · JIAQIAOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 1 person in 1 place, about 2 a week over 1 days. Mostly on chroma-core/chroma. Tools named alongside: PyPI.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "gpu-access" rule about Chroma. First post Oct 15, 2026, latest Oct 15, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
PyTorch GPU access and drivers are painfulNVIDIA GPU access and drivers are painfulDeepSeek GPU access and drivers are painfulGPU access, drivers and CUDA versions are painfulvLLM GPU access and drivers are painfulClaude Code GPU access and drivers are painfulOllama GPU access and drivers are painful
Other Chroma problems
History
Chroma GPU access and drivers are painful (2 posts)