Bytebuddy memory leak

[1057105012]

This problem occurred in the bytecode conversion phase. When I used a ByteBuddy agent to operate, I found that the loaded type type would not be unloaded, and the meta space and out-of-heap memory would keep growing until the docker memory limit was triggered and crashed. At this point, the heap may only be 200 MB, but the out-of-heap memory is already 700 MB, and the key is that the out-of-heap memory is not being reclaimed

[raphw]

Then you must cache values somewhere. Byte Buddy does not pool objects internally.