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: Java heap space | ||
---|---|---|---|
Product: | editor | Reporter: | pmaselkowski |
Component: | Parsing & Indexing | Assignee: | Tomas Zezula <tzezula> |
Status: | NEW --- | ||
Severity: | normal | CC: | tmysik |
Priority: | P4 | ||
Version: | 8.1 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 219844 |
Attachments: | stacktrace |
Description
pmaselkowski
2015-09-10 08:49:22 UTC
Created attachment 156040 [details]
stacktrace
The is large (500K) list of Indexable-s. Reassigning to editor/parsing to investigate if it is possible to not to collect all Indexables at once. The problem is not from the real project set up but from the wrongly opened folder. There is a possibility to hold the file list to examine on disk when they are > some limit. But it will become complicated as they need to be split according to mime types. As Tomas Zezula pointed it's not a real project problem. It's more of a clash with automatic project detection. For instance: It' nice feature to have netbeans detect dir as project if it contains known project file, ie. composer.json for PHP projects. But when such composer.json is lying in ie. dev folder with lot of other project, netbeans would open it as a project. I don't see any wise solution to detect if it's a project or some garbage file. Except that it could show some confirmation if there are no "nbproject" dir - so user could decide to auto init project or not. Currently it automatically create "nbproject" dir. Adding Tomas Mysik (the PHP engineer) on cc. |