Bug 76288 - Infinite loop problem
Summary: Infinite loop problem
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: UI (show other bugs)
Version: 1.2.0   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Helen Beeken CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-14 13:32 EDT by Gerard Toonstra CLA
Modified: 2004-10-18 04:50 EDT (History)
0 users

See Also:


Attachments
Screenshots of progress bars and CPU utiliisation. (128.12 KB, application/x-zip-compressed)
2004-10-14 13:33 EDT, Gerard Toonstra CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerard Toonstra CLA 2004-10-14 13:32:29 EDT
Hi,

I've just started on AspectJ programming and would like to make use of the AJDT 
plugins for Eclipse. I downloaded and installed from the Install/Update feature 
in the Preferences menu.

At this time I did a restart. No project was converted to AspectJ at this time.
I noticed that the actions "refresh" and "build" for my standard Java projects 
do not complete, or when they do it takes an extraordinary long time. During 
all this time, the CPU utilisation jumps to a full 100% and make the system 
unusable. It is not possible to do anything else in Eclipse during this time.
When it completes, it's in the order of half or 1 minute.

During these actions, a progress bar appears on the screen. For some actions, 
this progress bar has the feature to put the action towards the background. 
Having done that however, other applications cannot receive window focus and 
the desktop is almost entirely locked. The only application that can receive 
focus is the taskmanager ( luckily ).

I am attaching three screenshots with the details. The TM shows the 100% 
utilisation, the other windows show detailed actions that Eclipse is at that 
time executing ( or appear to be executing ). It appears that it's in the phase 
of updating other UI components.

I have executed eclipse.exe using the "-debug" option to try to get more 
information ( maybe it's looping on exceptions or whatever ), but there's no 
info coming out when it is executing these actions, I do not know if it's 
possible to increase verbosity with other options.

During the looping, the memory does not grow extensively.

I am using actually the SDK version of eclipse, from the archive "eclipse-SDK-
3.0M9-win32.zip" on a Windows 2000 system.

I've tried to disable some features using the project properties options and 
the windows | preferences "AspectJ" pages, but to no avail.

When I remove the plugins and do a restart, all the actions can be executed as 
normal and no looping occurs anymore, so the problem seems to definitely occur 
when AspectJ is installed.

Please let me know how I can help to provide more information, as I am not an 
expert in debugging Eclipse or its plugins. If you require more info about my 
system, don't hesitate to contact.

Regards,

Gerard
Comment 1 Gerard Toonstra CLA 2004-10-14 13:33:47 EDT
Created attachment 15173 [details]
Screenshots of progress bars and CPU utiliisation.
Comment 2 Helen Beeken CLA 2004-10-15 03:31:58 EDT
Hi Gerard,

Could you try using the eclipse 3.0 final and seeing if you have the same 
problems? (the zip is eclipse-SDK-3.0-win32.zip). 

Thanks, Helen
Comment 3 Gerard Toonstra CLA 2004-10-15 09:31:46 EDT
Hi Helen,

With this drop eclipse-SDK-3.0-win32.zip I have no problems whatsoever. I've 
had to take some time to make sure my settings were the same to verify. AspectJ 
is installed in this final now and there's no performance degredation that I 
can notice.

I've noticed that when I close/open and build projects in this version, the 
option "Details>>" in the progress bar is locked. In the M9 build it was 
possible to see the details during open/close/build operations. Possibly the 
problem was related to the progress bar updates/details.

Regards,

Gerard

Comment 4 Helen Beeken CLA 2004-10-18 04:50:47 EDT
Hi Gerard,

Good to hear that everything's working for you in Eclipse 3.0 Final.

I'm therefore closing this bug.

Thanks, Helen