This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | RubyAttachType and URLAttachType classes are loaded on 1st and 2nd NetBeans startup | ||
---|---|---|---|
Product: | debugger | Reporter: | Oleg Khokhlov <ovk> |
Component: | Code | Assignee: | Martin Entlicher <mentlicher> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jtulach |
Priority: | P3 | Keywords: | PERFORMANCE, REGRESSION, TEST |
Version: | 6.x | ||
Hardware: | All | ||
OS: | Windows XP | ||
URL: | http://wiki.netbeans.org/FitnessViaWhiteAndBlackList | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | stacktrace |
Created attachment 82044 [details]
stacktrace
We do not load the service classes: changeset: 131287:26d8cdc783bc http://hg.netbeans.org/main/rev/26d8cdc783bc ContextAwareService and AttachType$ContextAware are loaded from layer filesystem, ContextAwareSupport is just a support class used in instance creation. Their loading is O.K. IMHO. Re: "Their loading is O.K. IMHO.", I also think it is unpreventable. Please also add the *AttachType classes into ide.kit/test/qa-functional/data/blacklist.txt and run ide.kit/test/qa-functional/src/org/netbeans/test/editor/GeneralSanityTest.java to really check they are not loaded now and will not be loaded in future. Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |
Performance test reports there is regression in 1st and 2nd NetBeans startup which is caused by the loading of following classes: > org.netbeans.modules.ruby.debugger.ui.RubyAttachType > > org.netbeans.modules.web.client.javascript.debugger.attach.URLAttachType comment from jtulach: "Bug for debugger to prevent loading these types just to find out whether connect action shall be enabled. Imho it can be turned into alwaysEnabledAction. org.netbeans.spi.debugger.ContextAwareService org.netbeans.spi.debugger.ContextAwareSupport org.netbeans.spi.debugger.ui.AttachType$ContextAware Probably related to the previous problem."