Immutable solution version
Webserver Crashes with - Thread starvation or clock leap detected
Complete solution
Shows how to fix webserver Crashes with - Thread starvation or clock leap detected. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Upgrade to the next maintenance release or newer, and reopen the issue if it persists. Fixed and backported to all releases starting with 0.15.
Steps
- The webserver crash ('Thread starvation or clock leap detected') came from a thread leak in the execution and logs-follow endpoints: those endpoints use SSE connections and open a consumer on the internal queue, and in some cases the connection was never closed so the consumer stayed open forever, pressuring webserver memory. Fixed and backported to all releases starting with 0.15. Upgrade to the next maintenance release or newer, and reopen the issue if it persists.
When to use
You are seeing this: Reported in Kestra: Webserver Crashes with - Thread starvation or clock leap detected. Use this skill when you run into "Webserver Crashes with - Thread starvation or clock leap detected".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
In gh:kestra-io/kestra#4754 (https://github.com/kestra-io/kestra/issues/4754), the reporter ran into this: Reported in Kestra: Webserver Crashes with - Thread starvation or clock leap detected. The verified resolution: The webserver crash ('Thread starvation or clock leap detected') came from a thread leak in the execution and logs-follow endpoints: those endpoints use SSE connections and open a consumer on the internal queue, and in some cases the connection was never closed so the consumer stayed open forever, pressuring webserver memory. Fixed and backported to all releases starting with 0.15. Upgrade to the next maintenance release or newer, and reopen the issue if it persists.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_8ciHcjAE-yYaUPveBPsjRQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Webserver Crashes with - Thread starvation or clock leap detected <span>— Vectle</span></a>