Created attachment 837195 [details]
java log from eclipse
Description of problem:
Eclipse crashes when I edit the java file or any other file inside of Eclipse
I'm developing android app inside eclipse but when I try to use normal java developing or android developing results are same.
Version-Release number of selected component (if applicable):
Eclipse version :
I'm using OpenJDK 1.7.0 and I tried with 1.8.0 also but still problem happened.
And I tried to open with terminal and It's created log file It's in alo attachment
Open Eclipse and try to edit java file and crashed
Steps to Reproduce:
2.Open Project / or create project
3.Edit "java" file or any other programing language file
"Steps to Reproduce" part happen always
Open Eclipse and do development without problem.
Does Eclipse crash when you try going into Help -> Help Contents ? Are you using the google-talkplugin on your system ?
I learnt later It was "google-talkplugin" problem shortly I can only use when I deleted. So we can close bug for this.
As a workaround you can try adding '-Dorg.eclipse.swt.browser.DefaultType=mozilla' at the end of your /etc/eclipse.ini file. This isn't an ideal solution (Fedora Eclipse doesn't support xulrunner for rendering so the internal web browser won't be usable, and certain hover text might not be properly formatted) but it should stop the crashes, and allow you to keep google-talkplugin installed.
I don't believe we have a bug to track the issue caused by Eclipse (using webkitgtk) + google-talkplugin within Fedora so I don't mind keeping this open to track the progress.
I added to line started testing for Eclipse. Thank for info. Yes It's works fine for now. I will track it then If anything happen or any change I will write to here and give info(s) and so on then.
See the F20 FAQ for this:
This ticket appears to be a duplicate of the problem in: https://bugzilla.redhat.com/show_bug.cgi?id=1040223
Another reference to this problem:
And at Eclipse.org:
(In reply to Roland Grunberg from comment #3)
> As a workaround you can try adding
> '-Dorg.eclipse.swt.browser.DefaultType=mozilla' at the end of your
> /etc/eclipse.ini file. This isn't an ideal solution (Fedora Eclipse doesn't
> support xulrunner for rendering so the internal web browser won't be usable,
> and certain hover text might not be properly formatted) but it should stop
> the crashes, and allow you to keep google-talkplugin installed.
> I don't believe we have a bug to track the issue caused by Eclipse (using
> webkitgtk) + google-talkplugin within Fedora so I don't mind keeping this
> open to track the progress.
That solved the issue in my case
'-Dorg.eclipse.swt.browser.DefaultType=mozilla' cannot solved my problem.
By the way, it seems that google-talkplugin-188.8.131.52-1 can work with eclipse.(google-talkplugin has updated resent). is it?
if google-talkplugin-184.108.40.206-1 solved this problem, we can close this issue.
it hangs also with google-talkplugin-220.127.116.11
I am seeing this issue too.
I see this problem with blue jeans plugin installed:
google-talkplugin-18.104.22.168-1.x86_64 is OK for me.
(In reply to Peter Schiffer from comment #10)
> I see this problem with blue jeans plugin installed:
Funny that you mention this. I've installed the blue jeans plug-in yesterday and today I see *a lot* (3 times in the past 3 hours so far) F20 eclipse crashes.
Bluejeans is known to be a problem. I've reported this to bluejeans but nothing happened in the last few months. I recommend to Eclipse users to uninstall bluejeans or run SWT_GTK3=1 SWT_WEBKIT2=1 eclipse which will make eclipse use the experimental WEBKIT2 support which runs plugins out of process so the crash should not happen.
(In reply to Alexander Kurtakov from comment #12)
> Bluejeans is known to be a problem. I've reported this to bluejeans but
> nothing happened in the last few months. I recommend to Eclipse users to
> uninstall bluejeans or run SWT_GTK3=1 SWT_WEBKIT2=1 eclipse which will make
> eclipse use the experimental WEBKIT2 support which runs plugins out of
> process so the crash should not happen.
Thanks for the heads-up Alex. Just to clarify, by "which runs plugins out of process" you mean which plugins that run out of process? eclipse plug-ins? webkit plug-ins? something else?
Sorry, I should have been clearer. Webkit2 runs its (webkit) plugins out of process so a crash in the webkit plugin should not crash the main webkit process.
OK, so stock eclipse on F20 is 4.3 (Kepler). Using that with SWT_GTK3=1 is unusable. I've been told there is a packaged eclipse Luna (4.4) using copr. Thanks Mat! I gave that a whirl and that seems to work OK (no more crashes with bluejeans installed). Last remaining issue is this upstream bug:
Thanks for linking to that, Severin, and thanks for giving a try!
I wrote up a blog about it here: http://mbooth101.github.io/eclipse-luna-for-fedora-20.html
One extra thing that is worth mentioning is that you may also need to change the "--launcher.GTK_version" option to 3 in your /opt/rh/eclipse-luna/root/etc/eclipse.ini file in order to get it running on GTK3.
I hope this helps someone!
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.