Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369058

Summary:	Eclipse crashes during auto-completion
Product:	[Eclipse Project] Platform	Reporter:	Luca Cavanna <cavannaluca>
Component:	SWT	Assignee:	Grant Gayed <grant_gayed>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	critical
Priority:	P3	CC:	amj87.iitr, cavannaluca, ericwill, satyam.kandula
Version:	3.7.1	Keywords:	needinfo
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Luca Cavanna

2012-01-19 05:50:32 EST

Build Identifier: 20110916-0149

While I'm writing code I try to import the class Mockito (which is in my classpath), I write Mock and then ctrl+space, when I choose the desired class and I press enter eclipse crashes, after some seconds of doing apparently nothing. I can't find any stacktrace in the .metadata/.log but I have a core dump and when I open it with gdb I read:

Missing separate debuginfo for /opt/eclipse/configuration/org.eclipse.osgi/bundles/593/1/.cp/libswt-webkit-gtk-3738.so
Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/3b/4888eb86d052678be74b37d60ac2f12e6038d1
Missing separate debuginfo for 
Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/97/1a273a5c5c1521e8990bf96fd256ba8a4761f8
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".

warning: "/usr/lib/debug/usr/lib/libicudata.so.46.0.debug": separate debug info file has no debug info
Core was generated by `./eclipse'.
Program terminated with signal 11, Segmentation fault.
#0  0x00dcab77 in ciEnv::get_method_from_handle(_jobject*) () from /opt/jdk1.6.0_30/bin/../jre/lib/i386/client/libjvm.so
Missing separate debuginfos, use: debuginfo-install google-talkplugin-2.6.2.0-1.i386 zlib-1.2.5-5.fc16.i686


I tried to execute the suggested command but they don't work, I get a "No packages to install" message as a result. When I execute eclipse from the terminal I don't any error anyway.

My operating system is Fedora 16 (3.1.8-2.fc16.i686.PAE).


Reproducible: Always

Steps to Reproduce:
1.Write Mock (while having Mockito within the classpath)
2.ctrl+enter
3.choose Mockito from the list of proposals

Comment 1 Ayushman Jain

2012-01-19 07:05:08 EST

Hi, looks like there is something with your project setup/code which triggers the crash, and to investigate we will need more info. Is it possible to attach your project here? Also, can you tell us what all plugins you have installed over and above the default ones?

Comment 2 Luca Cavanna

2012-01-19 07:40:21 EST

I could reproduce the crash even with a new workspace and a small maven project with just one test class. When I open test/src/test/TestEclipseBug.java and try to write the following two lines inside the test empty method

File f = Mockito.mock(File.class);
Mockito.when(f.getPath()).thenReturn("/directory");

I cannot reach the end. Eclipse goes in segmentation fault, but not always at the same moment.

You can download the whole workspace I'm working with through this link: http://dl.dropbox.com/u/4006874/workspace.zip . I'm using Eclipse Java EE IDE for Web Developers, the only plugin I added is m2e.

Thanks, let me know if I can help more.

Comment 3 Satyam Kandula

2012-03-19 10:17:36 EDT

I think the problem is with SWT.

Comment 4 Grant Gayed

2013-06-26 11:45:04 EDT

It's likely a general Browser widget problem, and would probably happen in other scenarios as well.  However it's difficult to investigate without more info because the Browser works well in general on Fedora 16, so it must be somehow related to your OS config, settings, etc.  Can you try the following:

1. Try your case with Eclipse 4.3 (just released today).  It has lots of fixes in the area of the Browser that could help your case.

2. If your case still crashes then try to find a full dump from the VM (if using an Oracle VM then its name would start with "hs_err_").  This could provide some helpful insight.

Comment 5 Eric Williams

2016-09-19 20:44:00 EDT

No response from original bug reporter in quite some time.