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.

Bug 44251

Summary: "InvalidObjectException: Object with MOFID [etc] no longer exists."
Product: java Reporter: Jesse Glick <jglick>
Component: UnsupportedAssignee: issues@java <issues>
Status: RESOLVED FIXED    
Severity: blocker Keywords: RANDOM
Priority: P2    
Version: 4.x   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Attachments: Stack trace
Log excerpt

Description Jesse Glick 2004-06-02 23:30:47 UTC
Observed on my console several times. No idea how
to reproduce.
Comment 1 Jesse Glick 2004-06-02 23:31:14 UTC
Created attachment 15446 [details]
Stack trace
Comment 2 Jesse Glick 2004-06-04 01:51:47 UTC
Happened to me again (040603), in different circumstances, after which
I kept on getting exceptions from code completion and had to shut down
and restart. Again, no idea how to reproduce; didn't seem to be doing
anything unusual, just editing a unit test and running it, which had
worked a number of types in the past fifteen minutes or so without
problems.
Comment 3 Jesse Glick 2004-06-04 01:53:43 UTC
Created attachment 15466 [details]
Log excerpt
Comment 4 Jesse Glick 2004-06-04 05:25:36 UTC
Happened again. I was just editing a couple of classes and moving some
methods around. The classes were uncompilable for a while - probably
not syntax errors, but missing imports, missing impls of abstract
methods, that sort of thing.

After it starts happening, the IDE is pretty well broken - any reparse
in the editor causes the exceptions to start popping up again. You
can't continue working until you restart.
Comment 5 Tomas Hurka 2004-06-22 08:41:43 UTC
Moved to new subcomponent java/javacore.
Comment 6 Jan Becicka 2004-07-16 14:58:26 UTC
*** Issue 44794 has been marked as a duplicate of this issue. ***
Comment 7 Jan Becicka 2004-07-16 14:59:10 UTC
Can be duplicate of issue 46208
Comment 8 Martin Matula 2004-07-16 22:48:06 UTC
Based on the stacktraces it seems that the problems were caused by
bugs in elements matching in javacore and some other bugs causing
storage inconsistencies. The bugs were fixed some time ago. Please
file a new issue in case you experience IOE again.
Comment 9 Quality Engineering 2007-09-20 11:55:43 UTC
Reorganization of java component