dlopen/dlclose in x86 trigger memory increasing on M1

Hi

If a x86 program use dlopen/dlclose to load/unload a dylib, it could trigger memory increasing on M1.

I am not sure whether it is a leak, leaks command shows no leak, but memory increasing with dylib category.

Dirty Clean Reclaimable Regions Category
  • -- --- --- ---


    1560 MB 0 B 0 B 1642 dylib
It could be reproduced every time even only dlopen/dlclose a dylib without doing anything.

Any idea?

dlopen/dlclose in x86 trigger memory increasing on M1
 
 
Q