This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-jbang-examples.git
commit c14089b0109134cd3716278eb4e81c6962d4cbe9 Author: Claus Ibsen <[email protected]> AuthorDate: Thu Jul 2 10:08:50 2026 +0200 Update memory-leak README for renamed CLI command Co-Authored-By: Claude <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- memory-leak/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/memory-leak/README.md b/memory-leak/README.md index 4a513cc..4fe7c2d 100644 --- a/memory-leak/README.md +++ b/memory-leak/README.md @@ -1,6 +1,6 @@ ## Memory Leak -This example simulates a memory leak for testing the JFR Old Object Sample diagnostic tool. +This example simulates a memory leak for testing the Memory Leak diagnostic tool. It runs three routes: - **cache-leak** — adds a 64 KB entry to a HashMap every 200ms (never evicts) @@ -15,10 +15,10 @@ It runs three routes: camel tui -Navigate to the **JFR Old Objects** tab and press **R** to start a dual recording. +Navigate to the **Memory Leak** tab and press **R** to start a dual recording. After both runs complete, the comparison table will flag `byte[]` and `HashMap$Node` as `growing` with high growth ratios, confirming the leak. ### Diagnose with CLI - camel cmd jfr-old-objects + camel cmd memory-leak
