Occasional memory leak in std mpsc channels and crossbeam channels #17178
Labels
affects-4.0
This bug affects 4.0.x versions.
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
affects-8.1
This bug affects the 8.1.x(LTS) versions.
affects-8.5
This bug affects the 8.5.x(LTS) versions.
impact/leak
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
This issue can occur if a sender installs the first block right after all receivers have disconnected and checked for any existing messages, causing a memory leak.
See upstream issue report: rust-lang/rust#121582
To fix this we need to
What version of TiKV are you using?
nightly, 2024-6-23
The text was updated successfully, but these errors were encountered: