Vladimir> If the only aim of creating a debug listeners menu is to avoid OOM, Philippe>Not only this one.
Can we start from the requirements then? (I might miss the original email) Philippe>The use case is "I want to debug my plan" I think the most surprising thing for newbies is that "listeners are inherited". Implementing pause/resume/breakpoint would be great. Have you considered creating duplicate entries for "View Results Tree"? For instance, display it under current menu and under "debug ..." at the same time. Philippe>I think when you use a View Results Tree even with logs, you are trying to debug errors no ? View Results Tree can: 1) "log all results". This is useful for debugging. 2) "log errors only". It should skip successfull responses and log only erroneous ones (e.g. the ones with failed assertions, etc). The second option is useful even for regular load testing, as it would enable investigation of concurrency issues. Number of errors should not be high => number of logged results would not be high => no OOM, no much overhead. Otherwise you would have hard time trying to figure out why test fails under load. Vladimir
