But wouldn't that mean that the instrumentations performed by the agent generate invocations into YourKit runtime methods which keep on allocating more and more memory?The problem is in the Java 7 VM, but is triggered only when agent performs bytecode instrumentation of loaded classes.
Or in other words, YourKit only gets to know that there is a new class generated, if some code injected by YourKit within that class is executed, like in <clinit>?
So, the issue is, like you said, really with the JVM TI profiling interface not reporting class loading and unloading events for those dynamically generated classes.