Are you sure this is a duplicate of #531376? Because it mentions that the problem is fixed in Eclipse 3.5.2 but the problem of this bug still occurs in 3.5.2. The stack trace is also different. And the referenced Eclipse bug report there mentions that the bug only occurs with assistive technologies turned on, but I have it set to off and the bug occurs.
Are you sure this is a duplicate of #531376? Because it mentions that the problem is fixed in Eclipse 3.5.2 but the problem of this bug still occurs in 3.5.2. The stack trace is also different. And the referenced Eclipse bug report there mentions that the bug only occurs with assistive technologies turned on, but I have it set to off and the bug occurs.