https://bz.apache.org/bugzilla/show_bug.cgi?id=59157
--- Comment #3 from Vladimir Sitnikov <[email protected]> --- -1 for such a split. 1) Such a split would complicate day-to-day activities since noone would remember which listeners are filed under which menu. 2) I'm not sure there is a consistent way to tell if a particular listener is a "debug" listener or not. In other words, "debuggness" of a listener might depend on the configuration. For instance, "View results in tree" is somewhat fine if configured to log errors only. 3) I think UI should be designed around use cases. I'm not sure there's a case like "I need a debug listener, thus I open <<debug listeners>> menu". If the only aim of creating a debug listeners menu is to avoid OOM, then other ways should be explored: A1) Store just 50MiB of "View Results Tree" data, then start to drop new data. A2) Mark problematic listeners (and parent nodes in tree) with some kind of red. -- You are receiving this mail because: You are the assignee for the bug.
