Eclipse abruptly shuts down on linux mint 16 when I use autocomplete(ctrl+space) while writing android code
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Eclipse |
Fix Released
|
Medium
|
|||
Linux Mint |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Eclipse was fine a day ago while I was writing C code but a few minutes into writing Android code, it starts shutting down abruptly. Am not sure exactly what's wrong but as soon as the auto complete panes appear, Eclipse shuts down and a java error log is created on my desktop...
In Eclipse bugs #404776, Jakub Adam (jakub-adam) wrote : | #4 |
Created attachment 229267
Example crash report
In Eclipse bugs #404776, Jakub Adam (jakub-adam) wrote : | #5 |
Created attachment 229268
Patch for the crash
In Eclipse bugs #404776, Grant Gayed (grant-gayed) wrote : | #6 |
Thanks for investigating this Jakub, targeting for 4.3. From the crash report:
Stack: [0x00007f3e62e0
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libsoup-
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
j org.eclipse.
In Eclipse bugs #404776, Grant Gayed (grant-gayed) wrote : | #7 |
*** Bug 405786 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Akurtakov (akurtakov) wrote : | #8 |
Grant,
Any plans to accept the patch soon? It is impossible to launch Kepler builds on Fedora 19 because of this.
In Eclipse bugs #404776, İsmail Dönmez (ismaildonmez) wrote : | #9 |
For a workaround add the following to the end of your eclipse.ini
-Dorg.eclipse.
In Eclipse bugs #404776, Akurtakov (akurtakov) wrote : | #10 |
(In reply to comment #6)
> For a workaround add the following to the end of your eclipse.ini
>
> -Dorg.eclipse.
Mozilla is even less reliable as it breaks with every firefox update ans SWT doesn't support recent xulrunner versions (20.0 here) -at least it wasn't last I checked.
In Eclipse bugs #404776, İsmail Dönmez (ismaildonmez) wrote : | #11 |
Works for me on openSUSE 12.3
In Eclipse bugs #404776, René (rkrell) wrote : | #12 |
In which environment, the same one with GNOME 3.8 (separate repository GNOME:STABLE) using libsoup 2.42.0? See also bug 405786.
Also in this report there was said "with recent versions of WebkitGTK+" (which is not a standard OpenSUSE 12.3)
(In reply to comment #8)
> Works for me on openSUSE 12.3
In Eclipse bugs #404776, İsmail Dönmez (ismaildonmez) wrote : | #13 |
Ah I am using GNOME:Stable:3.8 repo.
In Eclipse bugs #404776, René (rkrell) wrote : | #14 |
(In reply to comment #10)
> Ah I am using GNOME:Stable:3.8 repo.
I use apparently (almost) the same environment OpenSUSE 12.3 + GNOME:Stable:3.8 and it crashes. Before updating to GNOME:Stable:3.8 it didn't crash for several weeks of intensive work with Eclipse. Therefore I'd rather ask:
- You don't override -Dorg.eclipse.
- Did you try the Javadoc hovers in some open Java editor for a while?
In Eclipse bugs #404776, İsmail Dönmez (ismaildonmez) wrote : | #15 |
(In reply to comment #11)
> (In reply to comment #10)
> > Ah I am using GNOME:Stable:3.8 repo.
>
> I use apparently (almost) the same environment OpenSUSE 12.3 +
> GNOME:Stable:3.8 and it crashes. Before updating to GNOME:Stable:3.8 it
> didn't crash for several weeks of intensive work with Eclipse. Therefore I'd
> rather ask:
> - You don't override -Dorg.eclipse.
> - Did you try the Javadoc hovers in some open Java editor for a while?
1. I have -Dorg.eclipse.
2. Yes I did, I opened an Android project and checked docs for multiple functions. Works fine.
In Eclipse bugs #404776, René (rkrell) wrote : | #16 |
Oh Ismail, sorry, I think I got the message after I've noticed your comments above. You tried the workaround, not the standard Eclipse.
The workaround with the "mozilla" default type works for me, too, using Firefox 20 (xulrunner-
(In reply to comment #11)
> (In reply to comment #10)
> > Ah I am using GNOME:Stable:3.8 repo.
>
> I use apparently (almost) the same environment OpenSUSE 12.3 +
> GNOME:Stable:3.8 and it crashes. Before updating to GNOME:Stable:3.8 it
> didn't crash for several weeks of intensive work with Eclipse. Therefore I'd
> rather ask:
> - You don't override -Dorg.eclipse.
> - Did you try the Javadoc hovers in some open Java editor for a while?
In Eclipse bugs #404776, Grant Gayed (grant-gayed) wrote : | #17 |
(In reply to comment #5)
> Any plans to accept the patch soon? It is impossible to launch Kepler builds
> on Fedora 19 because of this.
A fix will be in for 4.3M7. I don't have a built WebKitGTK 2.0 to use yet, and I want to do a good test pass with it.
In Eclipse bugs #404776, Grant Gayed (grant-gayed) wrote : | #18 |
Fixed > 20130425, commit: http://
Logged bug 406605 for new problem with the WebKitGTK 2.0 default authentication prompter.
In Eclipse bugs #404776, Pwebster-ca (pwebster-ca) wrote : | #19 |
*** Bug 406736 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Daniel-megert (daniel-megert) wrote : | #20 |
*** Bug 407076 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Grant Gayed (grant-gayed) wrote : | #21 |
*** Bug 407208 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Sascha Baumeister (sascha-baumeister) wrote : | #22 |
Just wanted you to know that adding the line to eclipse.ini seems to work for me under Ubuntu Gnome 13.04, upgraded to Gnome 3.8.1. Will the fix be part of this summer's Juno successor?
If not, I think the workaround info needs somehow to be spread, because this bug renders Eclipse totally unusable on newer Gnome-based linux distros, and this entry seems somewhat hard to find using google ... I didn't, which is the reason I created the duplicate, and I fear I won't have been the last.
In Eclipse bugs #404776, Grant Gayed (grant-gayed) wrote : | #23 |
(In reply to comment #19)
> Will the fix be part of this summer's Juno successor?
Yes, it will be in the June 4.3 release.
In Eclipse bugs #404776, Jlmoya (jlmoya) wrote : | #24 |
The workaround didn't do it for me as eclipse 4.2.2 continues to crash. Does anyone have any other suggestion as to how to fix the problem? Would anyone be kind enough to explain how to apply the patch attached?
In Eclipse bugs #404776, Grant Gayed (grant-gayed) wrote : | #25 |
(In reply to comment #21)
To work around this with 4.2.2 you need to add two lines to the end of your eclipse.ini:
1. the line in comment 6
2. -Dorg.eclipse.
In Eclipse bugs #404776, Pwebster-ca (pwebster-ca) wrote : | #26 |
*** Bug 408680 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Pwebster-ca (pwebster-ca) wrote : | #27 |
*** Bug 411745 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Markus-keller (markus-keller) wrote : | #28 |
*** Bug 411948 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Thomas-skjolberg (thomas-skjolberg) wrote : | #29 |
Using this workaround with fedora 19 removes the crash but displays an empty information window for autocompletes (for ctrl-space); unusable.
-Dorg.eclipse.
-Dorg.eclipse.
In Eclipse bugs #404776, Akurtakov (akurtakov) wrote : | #30 |
(In reply to comment #26)
> Using this workaround with fedora 19 removes the crash but displays an empty
> information window for autocompletes (for ctrl-space); unusable.
>
> -Dorg.eclipse.
> -Dorg.eclipse.
Thomas, do you see this problem with 4.3 final? I don't see the crash with both Eclipse from Fedora(yum install eclipse) and downloaded one from Eclipse.org. Fedora ships with xulrunner 22 which is not supported by swt.
In Eclipse bugs #404776, Thomas-skjolberg (thomas-skjolberg) wrote : | #31 |
Upgrading to 4.3 works perfectly, thanks.
In Eclipse bugs #404776, Mpol-l (mpol-l) wrote : | #32 |
The workaround seems to work on Indigo with xulrunner 17.
In Eclipse bugs #404776, Pwebster-ca (pwebster-ca) wrote : | #33 |
*** Bug 417037 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Pwebster-ca (pwebster-ca) wrote : | #34 |
*** Bug 417542 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Dan Winship (danw-gnome) wrote : | #35 |
Comment on attachment 229268
Patch for the crash
> long /*int*/ originalAuth = WebKitGTK.
>- WebKitGTK.
>+ if (originalAuth != 0) {
>+ WebKitGTK.
>+ }
> OS.g_signal_connect (session, WebKitGTK.
>- WebKitGTK.
>+ if (originalAuth != 0) {
>+ WebKitGTK.
>+ }
FWIW, the lookup/
In Eclipse bugs #404776, Jeremiah-renfro (jeremiah-renfro) wrote : | #36 |
FWIW I found this thread because I was getting a similar crash after updating OpenSUSE to 13.1 and eclipse to Kepler (eclipse.
Here is the tail of the console log:
No bp log location saved, using default.
[000:000] Browser XEmbed support present: 1
[000:001] Browser toolkit is Gtk2.
[000:001] Using Gtk2 toolkit
No bp log location saved, using default.
Adding -Dorg.eclipse.
In Eclipse bugs #404776, Grant Gayed (grant-gayed) wrote : | #37 |
(In reply to Jeremiah Renfro from comment #33)
Are you sure you're seeing the same crash (the dump file from your JRE indicates that it's in the soup_session_
In Eclipse bugs #404776, Jeremiah-renfro (jeremiah-renfro) wrote : | #38 |
(In reply to Grant Gayed from comment #34)
> (In reply to Jeremiah Renfro from comment #33)
>
> Are you sure you're seeing the same crash (the dump file from your JRE
> indicates that it's in the soup_session_
> this was a simple null check, and I haven't heard of anyone else seeing it
> since the fix went in. Maybe you're seeing bug 400626?
Maybe I am experiencing 400626, thanks for pointing me there, I'll start tracking that one also.
In Eclipse bugs #404776, Pwebster-ca (pwebster-ca) wrote : | #39 |
*** Bug 426031 has been marked as a duplicate of this bug. ***
Collins Mucheru Njoroge (collinsmucheru-k) wrote : | #1 |
Jackson Cleary (jacksonweekes) wrote : | #2 |
Hi Collins,
I believe this is an Eclipse Bug ( https:/
Solution posted on that page helped me, just add the following line to the end of the eclipse.ini file:
-Dorg.eclipse.
Hope that helps
Jackson
Changed in linuxmint: | |
status: | New → Confirmed |
Changed in eclipse: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
chemicalfan (mike-lumsden) wrote : | #40 |
Apparently this is now fixed in Eclipse - OP, can you test the new version to confirm this?
Collins Mucheru Njoroge (collinsmucheru-k) wrote : Re: [Bug 1270919] Re: Eclipse abruptly shuts down on linux mint 16 when I use autocomplete(ctrl+space) while writing android code | #41 |
I wil definetely do so, Thank you.
On Thu, Apr 10, 2014 at 3:22 PM, chemicalfan <email address hidden>wrote:
> Apparently this is now fixed in Eclipse - OP, can you test the new
> version to confirm this?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Eclipse abruptly shuts down on linux mint 16 when I use
> autocomplete(
>
> Status in Eclipse:
> Fix Released
> Status in The Linux Mint Distribution:
> Confirmed
>
> Bug description:
> Eclipse was fine a day ago while I was writing C code but a few
> minutes into writing Android code, it starts shutting down abruptly.
> Am not sure exactly what's wrong but as soon as the auto complete
> panes appear, Eclipse shuts down and a java error log is created on my
> desktop...
>
> To manage notifications about this bug go to:
> https:/
>
In Eclipse bugs #404776, Unnikrishnanadoor (unnikrishnanadoor) wrote : | #42 |
(In reply to Alexander Kurtakov from comment #7)
> (In reply to comment #6)
> > For a workaround add the following to the end of your eclipse.ini
> >
> > -Dorg.eclipse.
>
> Mozilla is even less reliable as it breaks with every firefox update ans SWT
> doesn't support recent xulrunner versions (20.0 here) -at least it wasn't
> last I checked.
I had the same problem in LinuxMint (petra), adding Dorg.eclipse.
In Eclipse bugs #404776, Arunkumar-thondapu-i (arunkumar-thondapu-i) wrote : | #43 |
*** Bug 434588 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Pwebster-ca (pwebster-ca) wrote : | #44 |
*** Bug 439082 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, P-sub (p-sub) wrote : | #45 |
*** Bug 440571 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Michael Vorburger (mike-vorburger) wrote : | #46 |
I can confirm that using Eclipse Luna v4.4 on Ubuntu 14.04 this doesn't happen anymore. For older Eclipse versions (e.g. 3.7.2) the -Dorg.eclipse.
In Eclipse bugs #404776, Pwebster-ca (pwebster-ca) wrote : | #47 |
*** Bug 442630 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Arunkumar-thondapu-i (arunkumar-thondapu-i) wrote : | #48 |
*** Bug 443457 has been marked as a duplicate of this bug. ***
Patochem (pmullot) wrote : | #49 |
-Dorg.eclipse.
On HP EliteBook
DISTRIB_
DISTRIB_RELEASE=17
DISTRIB_
DISTRIB_
NAME="Ubuntu"
VERSION="14.04.1 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.1 LTS"
VERSION_ID="14.04"
Peter Horsley (peter-g-horsley) wrote : | #50 |
I could reproduce this on Eclipse 4.2.2 after I upgrade from mint 13 to mint 17. After upgrading to Eclipse 4.4 (by adding the 'luna' repo - see https:/
In Eclipse bugs #404776, Arunkumar-thondapu-i (arunkumar-thondapu-i) wrote : | #51 |
*** Bug 454196 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Arunkumar-thondapu-i (arunkumar-thondapu-i) wrote : | #52 |
Backported this fix to 4.2.2+ via http://
In Eclipse bugs #404776, Marcolof (marcolof) wrote : | #53 |
This bug (or very similar one) appears to have reappeared in the latest update to Luna (20150219-0600). The same workaround also works there (e.g.
-Dorg.eclipse.
In Eclipse bugs #404776, Daniel-megert (daniel-megert) wrote : | #54 |
*** Bug 468562 has been marked as a duplicate of this bug. ***
In Eclipse bugs #404776, Sascha Baumeister (sascha-baumeister) wrote : | #55 |
(In reply to Marco Rietveld from comment #46)
> This bug (or very similar one) appears to have reappeared in the latest
> update to Luna (20150219-0600). The same workaround also works there (e.g.
> -Dorg.eclipse.
Just to let you know, I use the latest Eclipse Luna releases on Ubuntu Gnome 14.04.2 (both the Java and the C/C++ flavors), and have not experienced this problem again since the Juno versions (see comment #19). Therefore, I guess there must be something special in your setup.
Mentioning this 2 years old comment, I was probably right to predict that there'd be tons of duplicates for this bug; the bug description is simply not expressive enough to find it using a standard google search ...
In Eclipse bugs #404776, Arunkumar-thondapu-i (arunkumar-thondapu-i) wrote : | #56 |
(In reply to Marco Rietveld from comment #46)
> This bug (or very similar one) appears to have reappeared in the latest
> update to Luna (20150219-0600). The same workaround also works there (e.g.
> -Dorg.eclipse.
Please provide more details - which OS, what are the versions of GTK+ and webkit etc. and the crash logs too if possible.
In Eclipse bugs #404776, Arunkumar-thondapu-i (arunkumar-thondapu-i) wrote : | #57 |
*** Bug 474112 has been marked as a duplicate of this bug. ***
Created attachment 229266
Patch for the crash
With recent versions of WebKitGTK+, Eclipse crashes whenever Javadoc hover help is to be displayed in Java editor.
Looks this happens because WebKit doesn't attach a default Authenticate listener and therefore WebKitGTK. soup_session_ get_feature( ) returns 0 in WebKit.create(). See attached patch for fix.
Reproduced with all 3.8, 4.2 and 4.3 versions of SWT.