Unfortunately, there is no direct way to identify a lambda, because lambdas have no name by nature. At runtime, lambdas are currently implemented with anonymous classes. They are numbered sequentially after the $ sign relative to the containing class.
If you enable line number resolution in the JProfiler parameter (session settings-> tab profiling-> configure-> on the "record the method call" tab), you will see the line number in the "run" method in the trail of the back spot, which should help you find the lambda if this is the only lambda on this line.
source share