| Summary: | Opening a corrupted workspace causes CDT parser to use up all java heap | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Martin Swiezawski <marcin.swiezawski> |
| Component: | cdt-parser | Assignee: | Project Inbox <cdt-parser-inbox> |
| Status: | NEW --- | QA Contact: | Jonah Graham <jonah> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug, yevshif |
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Martin Swiezawski
Actually I can't attach a large .zip, I can send it separately. What is the maximum heap size you are using when running into this issue? I was using the default setting of 384. I enabled the display of java heap display and if I am quick enough when I hit recycle bin to garbage collect, then heap goes down a lot and then sits there for 2-3 seconds, then whatever process kicks of parsing starts again and java heap gets used up very quickly. The project is not large maybe 15-20 source files and it takes about 15-20 seconds for the heap to get used up once the process starts. Can you try to delete <workspace>/.metadata/.plugins/org.eclipse.cdt.core ? That worked around this issue. Heap is steady and no messages asking to exit. I assume that the files had been parsed using a wrong character encoding. This would lead to a lot of useless information in the index. When loading this information, the OutOfMemoryError can occur. I would be very surprised if encoding was changed from defaults. I checked with the customer and their response was "what encoding". Would workspace .metadata help? or project itself? I think I should be able to attach both if I separate them out. |