Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370951 - Eclipse crashes after selecting an entry in code completion
Summary: Eclipse crashes after selecting an entry in code completion
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7.1   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-08 08:54 EST by Elvis Dominguez CLA
Modified: 2012-03-21 05:53 EDT (History)
4 users (show)

See Also:

Attachments
hserr (102.99 KB, text/plain)
2012-02-08 08:55 EST, Elvis Dominguez CLA 		no flags Details
another hserr (109.06 KB, text/x-log)
2012-02-22 10:06 EST, Elvis Dominguez CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Elvis Dominguez CLA 2012-02-08 08:54:29 EST 
Build Identifier: Version: Indigo Service Release 1 Build id: 20110916-0149

This problem can't be reproduced every time.
I'm coding, ctrl+space to call code completion.
Code completion appears, i select an entry and the application freezes and then crashes.

Platform: Ubuntu 12.04 64bit
Java: 1.6.0_29



Reproducible: Sometimes

Steps to Reproduce:
1.call code completion via ctrl+space
2.
3.
Comment 1 Elvis Dominguez CLA 2012-02-08 08:55:23 EST 
Created attachment 210734 [details]
hserr
Comment 2 Elvis Dominguez CLA 2012-02-08 08:56:08 EST 
I have tried with java 7u2 but same behavior
Comment 3 Elvis Dominguez CLA 2012-02-21 10:50:45 EST 
Tested with java 7 u03 but same issue.
Opening a browser window crashes too. Maybe related to toolkit?
Comment 4 Elvis Dominguez CLA 2012-02-22 10:06:25 EST 
Created attachment 211407 [details]
another hserr
Comment 5 Elvis Dominguez CLA 2012-03-21 05:53:43 EDT 
I set this bug as resolved / invalid because the new Ubuntu Precise updates have fixed the buggy behaviour, thus is a libgtk bug (now fixed)