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: | OutOfMemoryError | ||
---|---|---|---|
Product: | java | Reporter: | bobtreacy <bobtreacy> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | blocker | CC: | pnejedly, rkubacki |
Priority: | P1 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | messages.log |
Description
bobtreacy
2007-02-07 17:11:25 UTC
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. |