ExampleKotlinPluginLoader VS scouter

So, I am writing a thing that takes plugins. It has to be in a JVM based language because of what I will be interfacing with so i chose kotlin. I need it to be able to dynamically open AND close the plugins. But it is hard to close them completely. I thought I had it, and then I learned to use a profiler and it turns out, I am not actually unloading them, only cutting them off from loading more things.... I made an example repo with just the loader setup, simplified api and launcher sections for people to look at. Help. Im so lost. I think im clearing all references to the plugin jar but the JVM just wont let go of the thing... Here is said example repo of said plugin loading setup. It says theres java. Dont worry. Thats copy-pasted in there as an example plugin for fun, but the simple plugins that are actually in kotlin have the same issue.... it also happens with or without the second function in the plugin interface... Fired up JVisualVM and now Im so confused.... You can pretty much ignore the exampleplugin folder unless you want to see a shitty minesweeper game hahaha. Main starts in exampleParentLoader, and then after the 1 main file sets up the 2 main loaders you move to examplepluginloader for the main part of the program https://github.com/BirdeeHub/ExampleKotlinPluginLoader Big changes are fine. The main program I'm making doesn't have a ton of stuff extra on top of it yet. It just needs to properly unload the plugins.

Scouter is a powerful tool that can monitor Redis, Nginx, Kafka, MongoDB, Kubernetes, and other sources. It can monitor CPU, memory network and heap utilization, active users, active services, and more.

💻 GitHub