One possibility is that you are not properly harvesting thread or child
exit status. That is not a memory leak exactly. You have to start
threads in a detached state to prevent the return status from collected.
Could something like that be happening?
On 1/23/2024 2:45 AM, yfliu2008 wrote:
G
There is instrumentation in ostest that prints heap usage after each
test test. That should isolate the memory leak.
On 1/19/2024 2:07 AM, yfliu2008 wrote:
Dear experts,
With "rv-virt/knsh32", I noticed the "used Kmem" shown by "free" command keeps growing
after each run of "ostest", belo
