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.
This morning a developer on my team who is using NetBeans 5.5 on Windows XP reported that she was suddenly getting OutOfMemoryError. Shortly after that my ide NB 5.5.1 on Mac OS X suddenly became sluggish and then ran out of memory as well. I have a large messages.log file, but I am not seeing how to send it to you. Please mail me at rtreacy@hmdc.harvard.edu with info on where to send the file partial sample javax.jmi.reflect.InvalidObjectException: Object with MOFID 1A7A5385-A25A-11DB-9F1C- DEAE4507AA77:0000000000001188 no longer exists, class: org.netbeans.jmi.javamodel.AttributeValue$Impl at org.netbeans.mdr.handlers.BaseObjectHandler._getDelegate(BaseObjectHandler.java:365) ... ... [org.netbeans.mdr.Logger] INFORMATIONAL *********** Exception occurred ************ at 11:25 AM on Feb 7, 2007java.lang.Exception: mofId: 1A7A5385-A25A-11DB-9F1C- DEAE4507AA77:0000000000001188, class: org.netbeans.jmi.javamodel.AttributeValue$Impl at org.netbeans.mdr.handlers.InstanceHandler.refDelete(InstanceHandler.java:313) at org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.deleteCollection (SemiPersistentElement.java:489) ... ... [org.netbeans.mdr.Logger] INFORMATIONAL *********** Exception occurred ************ at 11:25 AM on Feb 7, 2007org.netbeans.mdr.persistence.StorageTransientDataException: javax.jmi.reflect.InvalidObjectException: Object with MOFID 1A7A5385-A25A-11DB-9F1C- DEAE4507AA77:0000000000001188 no longer exists, class: org.netbeans.jmi.javamodel.AttributeValue$Impl at org.netbeans.mdr.persistence.btreeimpl.btreestorage.BtreeDatabase.writeStreamable (BtreeDatabase.java:885) at org.netbeans.mdr.persistence.btreeimpl.btreestorage.BtreeDatabase.replaceRecord(BtreeDatabase.java: 954) at org.netbeans.mdr.persistence.btreeimpl.btreestorage.BtreeDatabase.save (BtreeDatabase.java:527) at org.netbeans.mdr.persistence.btreeimpl.btreestorage.BtreeDatabase.commitChanges (BtreeDatabase.java:447) at org.netbeans.mdr.persistence.btreeimpl.btreestorage.BtreeStorage.commitChanges(BtreeStorage.java: 325) at org.netbeans.mdr.storagemodel.MdrStorage.save(MdrStorage.java:576) at org.netbeans.mdr.storagemodel.MdrStorage.commit(MdrStorage.java:547)[catch] at org.netbeans.mdr.util.TransactionMutex.end(TransactionMutex.java:83) at org.netbeans.modules.javacore.ExclusiveMutex.leave(ExclusiveMutex.jav ... ... Exception in thread "MDR event dispatcher" java.lang.OutOfMemoryError: Java heap spacejava.lang.OutOfMemoryError: Java heap space *********** Exception occurred ************ at 11:33 AM on Feb 7, 2007java.lang.OutOfMemoryError: Java heap space *********** Exception occurred ************ at 11:33 AM on Feb 7, 2007java.lang.OutOfMemoryError: Java heap space *********** Exception occurred ************ at 11:34 AM on Feb 7, 2007java.lang.OutOfMemoryError: Java heap space *********** Exception occurred ************ at 11:34 AM on Feb 7, 2007 java.lang.OutOfMemoryError: Java heap space *********** Exception occurred ************ at 11:34 AM on Feb 7, 2007 java.lang.OutOfMemoryError: Java heap space *********** Exception occurred ************ at 11:34 AM on Feb 7, 2007 java.lang.OutOfMemoryError: Java heap space *********** Exception occurred ************ at 11:37 AM on Feb 7, 2007
Created attachment 38188 [details] messages.log
Probably OOME is just a results of some other problems. First of them is EOFException when readin lookup cache. It is possible that application data are stored in /Users/roberttreacy/.netbeans/5.5.1dev are corrupted. ading Petr to cc:
I know little about lookup cache, but if it fails loading the cache for any reason, it just use the primary data directly, so the initial exception is just a symptom, not a cause. The fact that the lookup cache was "short" means either unclean shutdown of the IDE (killed in the middle of the previous session shutdown) or a lack of disk space on the system. Both of the mentioned causes would very probably cause corruption of MDR as well. How does this relate to the reported OOME? I'm not sure, but broken MDR may force the infrastructure to parse the data from source instead of MDR, which is much more memory consuming. It may also render some caches ineffective.