Bug 45168 - Eclipse 3.0M4 perform exhausting operations (freeze) on incremental (small) builds
Summary: Eclipse 3.0M4 perform exhausting operations (freeze) on incremental (small) b...
Status: RESOLVED DUPLICATE of bug 44443
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-18 19:30 EDT by Dennis Stetsenko CLA
Modified: 2003-10-20 16:30 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Stetsenko CLA 2003-10-18 19:30:55 EDT 
OS: WinXP and Win2000
JDK: JRE1.4.1 and JRE1.4.2
Eclipse Version: all 3.0 (M1, M2, M3 and especially bad on M4)
PC: 800MHz+512MB, 2.5GHz+1GB
Works fine on 2.1 release.

After full upgrade (by erasing old version, leaving just workspace in separate
dir) and first full re-build any attempt to perform small modification (even
comments correction) and save cause to wait for few seconds (at least 15 seconds
in a best case scenario). Last attempt with 3.0M4 consume all OS resources and
lasted up to 5 minutes (I'm talking about incremental builds, since I've made
full re-build before). Had to revert to 2.1 release. 
I can provide any additional information
Helpful (IMHO) information
1. javaw.exe process consumed all (99.9) CPU for all time eclipse was hanging
2. project size is quite big (>5Mb of source code)
3. any preference settings that could affect it (IMHO) was off (no decoration
etc, in 3.0M4 machine performance was reported to be small - did not work, fast
- did not work either)
4. almost all compile warnings was on (switched from default value - "ignore")
Comment 1 John Arthorne CLA 2003-10-20 11:07:56 EDT 
Try turning off filtering in the tasks and problems view to see if that speeds
it up.  There is a recent bug causing filtering based on selection or working
set to be very slow.
Comment 2 Dennis Stetsenko CLA 2003-10-20 16:22:40 EDT 
John, thanks a lot - your workaround helps. Please correct me if I found wrong
duplicated problem (#28162).

*** This bug has been marked as a duplicate of 28162 ***
Comment 3 John Arthorne CLA 2003-10-20 16:29:25 EDT 
Wrong dup.
Comment 4 John Arthorne CLA 2003-10-20 16:30:13 EDT 

*** This bug has been marked as a duplicate of 44443 ***