[BUG] Linux chip-tool : Memory may leak when try to control device after subscription

[MengdiHe]

Reproduction steps

step 1.start linux chip-tool in interactive mode
./chip-tool interactive start
step 2.use chip-lighting-app as TH, and commission it using linux chip-tool
pairing onnetwork 10 20202021
step 3.send on/off command to chip-lighting-app
on-off on 10 1
step 4.Repete step 4 maybe 10 or 20 times. Compare memory difference
ps aux | grep chip-tool
Then you can see that the VMRSS will grow instantly， or you can use cat /proc/[pid]/status, you will see that the vmdata keep growing after every command

Bug prevalence

Whenever I do this

GitHub hash of the SDK that was being used

e2fa6ba

Platform

other

Platform Version(s)

ubuntu 22.04

Anything else?

Actually, I tried it on Nov 2022 sdk version, which has the same result of the version above.
I don't know if I missed some key points.
We are now developing the controller program based on the chip-tool program. It will be appreciated if you can answer this issue!

[MengdiHe]

Finally I find that it's related with the pesistentstorage that will be init every time.
So I add a member value to record the name. If init next time, compare name with the record name first, and return directly if they are same. I dont know if this is a right way to solve this problem......

[MengdiHe]

Finally I find that it's related with the pesistentstorage that will be init every time. So I add a member value to record the name. If init next time, compare name with the record name first, and return directly if they are same. I dont know if this is a right way to solve this problem......

I find the following code comment:

// TODO: It's pretty weird that we re-init mCommissionerStorage for every
// identity without shutting it down or something in between...

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.