- Shipped
- September 28, 2026 at 9:38 PM UTC
- Author
- Kamo
- Commit
- d875d84
The image starts java -Xmx${JIGASI_MAX_MEMORY:-3072m} and the container was limited to 1Gi: the heap could outgrow the container, and Jigasi was OOMKilled mid-meeting (exit 137 at 21:36 on 2026-09-28, SP14 Task 31), dropping the AI's and every other SIP leg of every meeting at once. JIGASI_MAX_MEMORY 1280m and a 2Gi limit (512Mi requested): the rest of the container is libMeet's native media memory, threads and metaspace, as Kamo's rule for Java pods says. checksum/config is recomputed, so the push restarts Jigasi with the new heap.