Community
Participate
Working Groups
Have just upgraded to Ganymede yesterday [trying to use the TPTP for profiling a memory leak], and re-setting up my environment. Re-created my development projects, and go to attach the source to jars I have in a new user library and the process never returns from clicking Apply or OK on the "Properties for <jarname>.jar" - Java Source Attachment window. To reproduce I have a new Java Project. I have a user library with multiple jars. Locate jar to which source is to be attached RMB click - Properties Select Java Source Attachment Click External Folder Browse to Folder Click Open Click Apply or OK Cursor change to hourglass and never returns. Environment Project Source and Jars are held in ClearCase - snapshot view. Attaching source is held on network drive, though occurs when copied to c:\tmp\ Note: I could not see a duplicate defect, but there is similarity to and possibly related to the bugzilla: 242029. Thanks...Andrew
Could you please attach a thread dump to this bug report? See http://wiki.eclipse.org/How_to_report_a_deadlock - thanks.
Created attachment 110852 [details] AdaptJ Stacktrace. Taken when CPU got to ~25% (or at least I tried to capture it then) Boris Bokowski requested a StackTrace. I did the same as last time - selected the jar, Properties, Attach Source, Folder, Browse, OK. Waited a few minutes watching the CPU. Was quiet (0-5%) for a while then started spiking towards 25%. Did not stay there. I tried to capture this as it went to one of the spikes. I then captured 3 more when it was low CPU (this seemed to be the last spike - thereafter it stayed low). These are attached next.
Created attachment 110853 [details] Second Stack Trace - Low CPU
Created attachment 110854 [details] Third Stack Trace - Low CPU
Created attachment 110856 [details] Fourth Stack Trace - Low CPU
It works for me, I assume that the issue is reproducible in your environment though. It looks like an issue with JNI calls. What JVM do you use? Could you try to reproduce the issue using different one?
We are using 1.5.0_11 and have tried 1.5.0_16 (not just me who is getting this - a few of my colleagues are as well. We are having to stay with 1.5 as the vendor product we are working against / with is still having issues with their migration to 1.6 and will not certify with 1.6 yet. We are hoping this gets resolved soon, but they are unable to commit to a date. Is there a means of putting this information in manually by editing a config file or registry entry? [Especially if it is a JDK version related issue.] I tried looking around in doco / web but could not find anything. Thanks again...Andrew
(In reply to comment #7) > Is there a means of putting this information in manually by editing a config > file or registry entry? [Especially if it is a JDK version related issue.] I > tried looking around in doco / web but could not find anything. > I'm not following you. Are you asking if there is a place (www/help/doc) where we can add an entry saying that the issue can occur? Go to Eclipse_installation_folder/readme/readme_eclipse.html. In the html file you can find Known issues section. Is it the place that you are trying to find? BTW, Jerome suggested that this can be a duplicate of bug 244979.
Sorry no, am asking if there is an alternate means of adding in the link, (ie. by editing the config file or whereever) where this information is stored, manually. Andrew
I can second this bug, It happened for me as well, when selecting external folder as source location. However, when I zipped the folder and selected that file insted, it worked.
Please continue the discussion in the JDT/Core bug report. *** This bug has been marked as a duplicate of bug 244979 ***
(In reply to comment #9) > Sorry no, am asking if there is an alternate means of adding in the link, (ie. > by editing the config file or whereever) where this information is stored, > manually. AFAIK, there is no other way.
