For applications that use reflection to load classes, a ClassNotFoundException is an exception like any other, which is (or should be) catched in the application itself. Unfortunately, while profiling, it causes the profiler to die because it cannot instrument the class. Would it be possible to simply ignore these cases so that the application code could get the ClassNotFoundException and deal with it itself.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.