Summary: | [RC2] Searches freezes ? | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Christophe Elek <celek> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.1 | ||
Target Milestone: | 2.1 RC3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Christophe Elek
2003-03-10 11:15:02 EST
You're getting OutOfMemoryErrors. Start eclipse.exe with -vmArgs -Xmx256Mb (and increase as needed). Let us know if this fixes the problem. You use -Xmx512M in your command line, but you should use -vmargs -Xmx512M. Ok to close? nope as I see two NPE in the log and I didn't get the OutOfMemory message on this one... I agree it may be caused by the OutOfMemory though :-) You do have OutOfMemoryError prior to NPE. Please try your test case with -vmargs -Xmx256M or more from a fresh workspace. I understand there is a OutOfMemory :-) My point is that, as a user, I didn't get the notification that an OutOfMemory occured (thus I was surprised that the dialog freezes) As an 'expert' user, looking at the log, I saw two NPE. so: 1) I agree that if OutOfMemory doesn't occur, the NPE may not occur but 2) If they occur, user will open bug. If we cannot prevent the OutOfMemory (and I think we can't) we should at least prevent the NPE, and maybe notify the user. At lest have in the log only OutOfMemory, and no NPE... no ? The problem is that the behavior is unpredictable after a OutOfMemoryError. Therefore the state of object might be unknown. If it is not easy to report an OutOfMemoryError because it might not be possible to open a dialog without getting another OutOfMemoryError. It is a little like a snake eating its own tail. If increasing the heap size fixes this problem, I think this is the best we can do. ok, fair enough :-) Closed. Updated milestone. |