https://issues.apache.org/bugzilla/show_bug.cgi?id=40850
--- Comment #9 from Sebb <[EMAIL PROTECTED]> 2008-04-03 13:57:05 PST --- (In reply to comment #8) > I'm working on applying the patch to 2.3.1 now and should have a patch by the > end of the week. Thanks. > The essence of what the previous patch did was move the > bshClass.newInstance(); > call from the BeanShellInterpreter constructor to the bshInvoke method so a > new > interpreter instance is created each time to release the handle on the > previously parsed script objects. > > The downside of this approach is the extra object creation and the inability > to pass data between BSH runs other than through jMeter properties. Yes; that's why I've been wary of adding it. > As far as I > can tell from the BSH docs there is no way to give a bsh.Interpreter a script > and just a have it run that same script over and over. You can define methods in a startup file, and call that from the screen or another file. This reduces the new objects created. > I was thinking that this time around I could look at adding an option to the > UI > to either use a persistent Interpreter (realizing it leaks memory) or a > per-call Interpreter which won't leak memory. > It could be UI or a property. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
