You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/12/02 17:57:15 UTC

DO NOT REPLY [Bug 25141] New: - GUI components created at startup - causes harmless NPE in ProxyControlGui

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25141>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25141

GUI components created at startup - causes harmless NPE in ProxyControlGui

           Summary: GUI components created at startup - causes harmless NPE
                    in ProxyControlGui
           Product: JMeter
           Version: Nightly (Please specify date)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: jsalvata@atg.com


Some GUI components (e.g. the HTTP Proxy) are created at program startup -- I
don't know why. Some (well, the HTTP Proxy for one) will subscribe as listeners
to events from the tree, meaning they will stay there consuming memory forever.

We need to check whether the object creation is a bug or a feature, and in any
case clean the memory leak.

BTW, in the current code, this causes the following error every time the tree
changes:
ERROR - jmeter.gui.action.ActionRouter:  java.lang.NullPointerException
	at
org.apache.jmeter.protocol.http.proxy.gui.ProxyControlGui.reinitializeTargetCombo(ProxyControlGui.java:697)
	at
org.apache.jmeter.protocol.http.proxy.gui.ProxyControlGui.access$0(ProxyControlGui.java:670)
	at
org.apache.jmeter.protocol.http.proxy.gui.ProxyControlGui$1.actionPerformed(ProxyControlGui.java:567)
	at
org.apache.jmeter.gui.action.ActionRouter.postActionPerformed(ActionRouter.java:332)
	at org.apache.jmeter.gui.action.ActionRouter.performAction(ActionRouter.java:119)
	at org.apache.jmeter.gui.action.ActionRouter.access$0(ActionRouter.java:105)
	at org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter.java:99)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
	at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
	at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

Rather than preventing the NPE, I prefer to leave it there as a reminder that we
need to fix the original bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org