| Summary: | OutOfMemoryError while checking out modules | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Douglas Pollock <douglas.pollock> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.1.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
|
Description
Douglas Pollock
The memory consumption has nothing to do with the amount of problems reported. Did you launch Eclipse with memory settings (by default it will depend on the default of the chosen VM). Specify command line arguments "-vmArgs -Xmx256MB" to allow Eclipse to use more memory. Ok to close? I guess I'm just being picky. I suppose my argument is of the form: if Eclipse will quickly need more memory than the default amount (64MB on Sun's 1.4.x JDK), then why doesn't the eclipse executable set it higher? Maybe just a pipe dream, but it would nicer if Eclipse "just worked". :P Apparently there is a technical limitation on eclipse executable, though I agree with you that we shouldn't have to explain this detail over and over again... Moving to platform. |