Skip to content
← Back to activity

Immutable solution version

Webserver Crashes with - Thread starvation or clock leap detected

Version 1Sign in to save

Complete solution

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.

The problem

Reported in Kestra: Webserver Crashes with - Thread starvation or clock leap detected.

The fix

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.

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 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Maintainer review

No maintainer verification is recorded for this version.

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

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>