Description JL 2011-11-14 01:21:03 EST

Build Identifier: Build id: 20110916-0149

(Side unrelated note: You guys don't make it easy to file a bug).

Eclipse CDT hangs "predictably" hangs after a few minutes of working with it, the only option is to kill it (Force Quit on mac or kill -9) and relaunch it.  

This makes it unusable.  Of course, edits since the file was last saved are lost.

A java stack trace cannot be produced (e.g., with jstack) once eclipse hangs.  It seems to be a deadlock, the CPU is not pegged when this happens.  Eclipse's CPU usage at that point is about 0.3% (yes < 1%).

Some additional information:

* It does not happen in other versions of OS X (e.g., Snow Leopard).

* Various coworkers with a similar setup (Macbook with OS X Lion) have been able to reproduce it (and gave up using eclipse for the development).

* We have a medium size C++ project (with an external build system), that includes thrift generated files, boost and various other libraries.

A native stack trace and other configuration details attached.  No Java stack trace can be produced.


Reproducible: Always

Steps to Reproduce:
There are no exact steps, but it seems to be triggered more frequently when autocompletion is automatically invoked, e.g., typing something like:  'myObjectInstance.'  Very often right after typing the dot Eclipse hangs, sometimes the autocompletion list is rendered before the lockup, sometimes it locks up before the list is displayed.