davsclaus opened a new pull request, #29513:
URL: https://github.com/apache/camel/pull/29513
_Claude Code on behalf of davsclaus_
Found by running the `showcase/memory-leak` example. It leaks `byte[]` in
two routes: a cache in a lambda, and a buffer list in a processor class. After
a recording, the Memory Leak tab's samples table showed two lines that both
said `byte[]`. Only the allocation stack in the detail of each told them apart,
and the example's point is to show which route leaks.
The CLASS column now also says where the objects were allocated in the code
of the integration: the first frame of their stack that is not of the JDK or of
Camel (a lambda's generated class is skipped for its body):
```
# CLASS COUNT
SAMPLEDā¼ AGE
>> 2 byte[] in MemoryLeak.lambda$configure$0:21 86
5.4 MB 59s
1 byte[] in BufferLeakProcessor.process:45 119
3.7 MB 1m
```
The site comes from a new class, `LeakSite`. `MemoryLeakTab.java` is at its
`SourceSizeTest` line limit, so the change there is one line.
The help page (memory-leak.md) is updated.
Tests: `LeakSiteTest`, with the stacks of the example's recording. The full
`camel-jbang-plugin-tui` suite passes, apart from `ConfigurationTabRenderTest`,
which fails on main and is fixed by #29503.
š¤ Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
