Liclipse exits about once a day

[hess...@gmail.com]

Liclipse terminates at random times about once a day whether I'm using it or not.  The window just disappears.   I'm running it on  a remote computer (linux).  The terminal session on that remote computer that hosts it it stays open. 

For a week or so I ran Liclipse on my local linux computer and it did not crash. 

Is there some log I could look at?

[Fabio Zadrozny]

To try to get the error, you can try using the -XX:ErrorFile to specify the location where java should put errors so that it can give some tip on what may be happening (you need to put it in LiClipse.ini).

See: https://docs.oracle.com/javase/7/docs/webnotes/tsg/TSG-VM/html/clopts.html for more information.

Which Linux version are you using remotely?

Best Regards,

Fabio

--
You received this message because you are subscribed to the Google Groups "LiClipse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liclipse+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bret Hess]

Linux 2.6.32-642.6.2.el6.x86_64

OK I put that -XX:ErrorFile in the .ini file...and it no longer gives me the logger error when I start liclipse. :)   So I'll wait a while until it fails and see what the log says. 

--

Bret Hess
Department of Physics and Astronomy
Brigham Young University
N251 ESC
Provo, UT 84602
801-422-2108
FAX 801-422-0553

[Bret Hess]

Even with the  line

-XX:ErrorFile=/fslhome/bch/hessgroup2/software/liclipse/javaErrors.out

in my liclipse.ini file, I still get this error, which occurs some time after I start liclipse, so the logging isn't working.

log4j:WARN No appenders could be found for logger (org.eclipse.jgit.util.FS).
log4j:WARN Please initialize the log4j system properly.

[Fabio Zadrozny]

Hi Bret,

That log4j warning can be safely ignored (and it's not really affected by the -XX:ErrorFile argument which should be handled by the java vm).

Best Regards,

Fabio

[Bret Hess]

It's not writing anything to the log file given by -XX:ErrorFile when it exits.

[Bret Hess]

I also have an older Eclipse version running on the same remote computer that doesn't have this issue.

[Fabio Zadrozny]

Humm, which Linux and UI are you using? (Ubuntu, Cent OS / KDE, Gnome)

[Bret Hess]

On my local machine, I use Ubuntu with gnome classic, and within a terminal connected to the remote machine, I run Liclipse. 

The remote machine is running Linux 2.6.32-642.6.2.el6.x86_64

[Fabio Zadrozny]

But what's the flavor of the linux on the remote machine? (i.e.: you're posting the kernel info while I need more info on the actual Linux distribution).

[Bret Hess]

Red Hat Enterprise Linux 6.6

[Fabio Zadrozny]

My guess is that it's something related to SWT... try to ask LiClipse to use GTK 3 (i.e.: set the --launcher.GTK_version to 3 in LiClipse.ini and see if it works better).

It's also weird that it didn't generate an error log on the crash.

The docs say that it may also create an "hs_err_pidpid.log" in the working dir, application dir or in the temp dir... can you check if that file was created in any of those places?

[Bret Hess]

From your comment I see I should have said earlier that I get an error "Gtk-Message: Failed to load module "canberra-gtk-module"  everytime I start Liclipse, but I thought it was unrelated. 

I changed the version to 3.  I still get the above error. 

Thanks,

Bret

[Fabio Zadrozny]

Well, I'm not 100% sure on that, but can you install that module to see if it stops complaining? (i.e.: see: http://www.linuxquestions.org/questions/linux-software-2/gtk-message-failed-to-load-module-canberra-gtk-module-936168/)

Best Regards,

Fabio