Summary: | New GarbageCollection algorithm, makes my computer hanging every few seconds | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Karsten Becker <java> |
Component: | Runtime | Assignee: | platform-runtime-inbox <platform-runtime-inbox> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | john.arthorne |
Version: | 3.2 | Keywords: | vm |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Karsten Becker
2006-02-11 05:48:30 EST
Eclipse does not have any GC policy nor does it trigger the GC (or at least it should be pretty rare). I think that you should see the same problem with any other application and similar settings. My bets are that the heap is so huge that a GC takes a long time and requires so much CPU that it alters other processes. You should try with another VM. See: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5101898 Apparently fixed in 1.5.0_06 I suspect -Xmx1024M is overkill, since the cost of a full gc will be proportional to allocated heap size. You may actually get better performance with a *lower* max heap. |