Community
Participate
Working Groups
Build Identifier: 20110916-0149 Seemingly randomly when editing a file in eclipse indigo the IDE just freezes up and stops responding completely and indefinately. I can't seem to reproduce it using any particular methods thus it seems rather random. I removed my old installation of Eclipse and downloaded and installed a fresh new version thinking that may that would fix the issue but it continues to occur. Reproducible: Couldn't Reproduce Steps to Reproduce: I have tried to recreate the issue with the same steps but it happens randomly. I follow the same set of actions as the last time and it doesn't occur. Then I continue with my daily work and all of the sudden it happens again.
Get a thread dump when it occurs. http://wiki.eclipse.org/index.php/How_to_report_a_deadlock
Created attachment 204087 [details] heap dump from VisualVM 1.7.0 (Build 110325)
Created attachment 204088 [details] heap dump
(In reply to comment #2) > Created attachment 204087 [details] > heap dump from VisualVM 1.7.0 (Build 110325) This is a heap dump, not a thread dump.
Created attachment 204089 [details] Windows 7 Dump
Sorry, didn't see your request. I will get a few thread dumps also. I am actually able to reproduce it quite regularly now. I am just doing a find/replace of a value in my document and it happens between the 5th and 8th replace each time. (In reply to comment #1) > Get a thread dump when it occurs. > http://wiki.eclipse.org/index.php/How_to_report_a_deadlock
Created attachment 204090 [details] Thread Dump of Eclipse Process
Created attachment 204093 [details] thread dump of Eclipse process
Created attachment 204094 [details] Thread Dump of Eclipse Process
(In reply to comment #6) > Sorry, didn't see your request. > > I will get a few thread dumps also. Actually, it seems your hprof files also have thread dumps embedded in them. In any case, thanks for your uploads.
No problem. I also added three thread dumps. Here are the steps I was using to recreate the issue for the thread dumps. Steps to reproduce. 1. Press ctrl-f to do a "find" in my document on "playMenu" to find the correct spot in my document. 2. press the find button to move to the point in my code where "playMenu" first appears. 3. move the cursor to a line just above the "found" text. 4. with the "find/replace" dialog still open do a find/replace on "playMenu" replacing it with "delinquencyNotification". 5. after the 5th replace, type over the replaced text with the text "repeat" 6. click find again to find the next instance of "playMenu". 7. click on the found text and type "repeat" 8. click on the replace/find button 3 - 5 more times to replace the given value 9. IDE freezes. (In reply to comment #10) > (In reply to comment #6) > > Sorry, didn't see your request. > > > > I will get a few thread dumps also. > Actually, it seems your hprof files also have thread dumps embedded in them. In > any case, thanks for your uploads.
It appears that if I save the document after every two or three replace/find instances the issue doesn't occur. (In reply to comment #11) > No problem. I also added three thread dumps. > Here are the steps I was using to recreate the issue for the thread dumps. > Steps to reproduce. > 1. Press ctrl-f to do a "find" in my document on "playMenu" to find the correct > spot in my document. > 2. press the find button to move to the point in my code where "playMenu" first > appears. > 3. move the cursor to a line just above the "found" text. > 4. with the "find/replace" dialog still open do a find/replace on "playMenu" > replacing it with "delinquencyNotification". > 5. after the 5th replace, type over the replaced text with the text "repeat" > 6. click find again to find the next instance of "playMenu". > 7. click on the found text and type "repeat" > 8. click on the replace/find button 3 - 5 more times to replace the given value > 9. IDE freezes. > (In reply to comment #10) > > (In reply to comment #6) > > > Sorry, didn't see your request. > > > > > > I will get a few thread dumps also. > > Actually, it seems your hprof files also have thread dumps embedded in them. In > > any case, thanks for your uploads.
(In reply to comment #11) > 1. Press ctrl-f to do a "find" in my document on "playMenu" to find the correct > spot in my document. From your thread dumps it seems you are editing XML files, is this correct? If you try to reproduce the problem in some regular text file (with a .txt file extension) and use the context menu with > Open With > Text Editor, does the problem occur in a regular text editor?
Thanks for your bug report. Could you provide us with the file you've been working on? Do you have any other plug-ins installed? Are there any errors in your error log?
Unfortunately I am unable to provide you with a copy of the file. My employer won't allow me to do so. I have the following plugins installed: C/C++ Development Tools 8.0.0.201109151620 org.eclipse.cdt.feature.group Eclipse CDT C/C++ Development Tools SDK 8.0.0.201109151620 org.eclipse.cdt.sdk.feature.group Eclipse CDT Eclipse XML Editors and Tools 3.3.1.v201108102009-7H7EFZ3DxumTlaI6nheRdHo2p1KaDIL1Uz-S3PL org.eclipse.wst.xml_ui.feature.feature.group Eclipse Web Tools Platform The file I'm editing is in a "general" project and just houses VoiceXML files which I have associated with the XML Editor. (In reply to comment #14) > Thanks for your bug report. Could you provide us with the file you've been > working on? Do you have any other plug-ins installed? Are there any errors in > your error log?
Created attachment 204112 [details] .metadata\.log
Thanks for all of your help in trying to tackle this problem. Up to this point, I haven't been able to reproduce unfortunately, and I think that is essential in order to address this. Your thread dumps indicate that we're trying to obtain a lock that's already been acquired by some other thread. Unfortunately for us, that thread doesn't seem to be showing itself. It's possible that it's because the thread that did acquire that lock failed to release it. Without knowing that, it comes down to a guessing game. For this reason, I'm moving it into worksforme. If you do come across any other information that might help in pinpointing the problem, please reopen the defect and we'll take another look.
