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.
[ JDK VERSION : 1.6 ] While browsing a largeish java source file in a standard project. Navigator display seems to be using 100% of the cpu. javax.jmi.reflect.InvalidObjectException: Object with MOFID E9473653-6439-11DA-BB08-04255790AA77:00000000000023D5 no longer exists, class: org.netbeans.jmi.javamodel.Method$Impl at org.netbeans.mdr.handlers.BaseObjectHandler._getDelegate(BaseObjectHandler.java:359) at org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.getElementInfo(SemiPersistentElement.java:186) at org.netbeans.modules.javacore.jmiimpl.javamodel.CallableFeatureImpl.initChildren(CallableFeatureImpl.java:153) at org.netbeans.modules.javacore.jmiimpl.javamodel.MetadataElement.initCheck(MetadataElement.java:140) at org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.getElementInfo(SemiPersistentElement.java:185) at org.netbeans.modules.javacore.jmiimpl.javamodel.ParameterImpl.initChildren(ParameterImpl.java:345) at org.netbeans.modules.javacore.jmiimpl.javamodel.ParameterImpl.getTypeName(ParameterImpl.java:154) at org.netbeans.jmi.javamodel.Parameter$Impl.getTypeName(Unknown Source) at org.netbeans.modules.java.navigation.jmi.JUtils.getParameterType(JUti
Created attachment 27714 [details] ide log
Probably duplicate of some issue? Do you check isValid()?
Hmm, I don't think it is a duplicate. Situation is that code in navigator is running inside read transaction and checks validity of elements which lifetime spans beyond one transaction: ClassMemberModel, line 287: repo.beginTrans(false); try { fireBusyChange(true); // check validity if ( this.clazz != null && !this.clazz.isValid () ) { this.clazz = null; } The element mentioned in exception comes from jmi call in the same transaction, called after mentioned validity checks. After talk with jbecicka, I believe java navigation is using the API correctly, so perhaps error is on jmi side, passing back. Please ask me if you need any help, explanation of java navigation code, thanks.
It looks like different symptom of issue 63594. Javac died and left MDR in inconsitent state. This should be fixed in latest dev build. Can you reproduce this issue in latest dev? Thanks *** This issue has been marked as a duplicate of 63594 ***
Reorganization of java component