Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346657 - UI freeze on Ubuntu 11
Summary: UI freeze on Ubuntu 11
Status: CLOSED DUPLICATE of bug 322914
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.6.2   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-20 08:07 EDT by Doug Simon CLA
Modified: 2011-05-20 08:25 EDT (History)
1 user (show)

See Also:


Attachments
Contents of .metadata/.log (811 bytes, text/plain)
2011-05-20 08:09 EDT, Doug Simon CLA
no flags Details
Output of jstack on frozen Eclipse process (11.87 KB, text/plain)
2011-05-20 08:10 EDT, Doug Simon CLA
no flags Details
Another jstack capture (22.37 KB, application/octet-stream)
2011-05-20 08:19 EDT, Doug Simon CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Doug Simon CLA 2011-05-20 08:07:36 EDT
Build Identifier: M20110210-1200

I'm frequently experiencing a complete freeze of the Eclipse UI. It seems to happen after I resume my Linux box after a suspend and then make an edit to a Java editor frame. Unfortunately, it's not reliably reproducible. I will attach a copy of the Eclipse log as well as the output of jstack on the frozen Eclipse process. The only solution is to kill the process and relaunch Eclipse.

Reproducible: Sometimes
Comment 1 Doug Simon CLA 2011-05-20 08:09:16 EDT
Created attachment 196203 [details]
Contents of .metadata/.log
Comment 2 Doug Simon CLA 2011-05-20 08:10:01 EDT
Created attachment 196204 [details]
Output of jstack on frozen Eclipse process
Comment 3 Doug Simon CLA 2011-05-20 08:19:29 EDT
Created attachment 196207 [details]
Another jstack capture

This one occurred when hovering over a red-underlined problem in a Java editor.
Comment 4 Dani Megert CLA 2011-05-20 08:25:07 EDT

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