Eclipse crashes while running?
 

I stopped punishing myself with Eclipse 4 or 5 years ago. I found Eclipse on Linux to always be inferior to Eclipse on Windows, but it sucks on both. I switched over to Netbeans and I use Maven. I'll never go back but it does require more resources when projects are large, like several thousand class files.

Okay, that wasn't helpful to your particular problem. I still run Eclipse once in a while because it has more flexibility on set up than Netbeans. I found that when Eclipse would eat itself on Linux, I would spend hours trying to fix it. Eventually, I would just reinstall it and move on. It was always faster than trouble shooting it. I don't know what it is about Eclipse, maybe it is plugins that step on each other, or maybe SWT just isn't mature on Linux, I don't know. I keep the plugins to a minimum and I try not to breath on it too hard, because it has always seemed fragile to me.

Given my statements in the first paragraph, I understand that IDE preferences can start holy wars. Switching is intensely painful. It takes about a month to start feeling like you are comfortable and productive. At least that was my experience. So I never recommend switching unless someone is really willing to upset their whole work life for a couple of months.

I just fired up my Eclipse install on Slackware 13.1 just to make sure I didn't see your issue. I might be a little behind on my Eclipse version, Release 3.5.2 Last revised February 10, 2010. I'm running 64 bit if that matters to you as I don't know if there would be a difference there.

IDEs suck!

I agree, that in Java, most of our IDE choices have some real issues, although I have not used IntelliJ Idea. But you can't be reasonably productive without one. It's silly to try and do refactorings without something to help find all the places in code that need to be switched.

Debugging and profiling are much nicer on IDEs as well. Other essential things include code completion, Javadoc reference on the fly, and syntax highlighting.

On large projects, you just can't waste the time compiling unnecessarily to find issues. Even if you have perfect unit tests, it is still a waste of time to build when all you need is a progress check on your coding.

"IDEs suck" is both amusing and true, but they are essential tools for getting work done. We are expected to do more than we used to and handle larger systems. We need effective tools to do this in the short time frames we are generally given. Gone are the days of year or multi-year projects. Now it's days and weeks no matter how silly the deadline and corresponding scope.

Besides, at least Eclipse and Netbeans have vi bindings available. I seriously can't code without vi. I can't even think without vi.

remove seamonkey
 

I found that
find / -name libxpcom_core.so
/usr/lib/thunderbird-3.0.4/libxpcom_core.so
/usr/lib/seamonkey-<somthing_another>/libxpcom_core.so
and just remove seamonkey package. And everything work fine.

Or just remove Eclipse and don't worry about it ;-)

I'm sorry, I just couldn't help myself. I'll keep that in mind.

Netbeans 6.9 is pretty nice, very solid. I use it every day and I leave it up for days at a time with *no* crashes yet. Best version yet. But, it does require better hardware than Eclipse to run comfortably. It also is not as flexible as Eclipse on how you set up a project. If you use Maven, it doesn't matter. Maven makes all projects in all IDE's equal on setup.

One last thing, I upgraded Thunderbird to Slackware's current which is 3.1. The stable branch is 3.0.5. I found 3.0.5 very buggy and it crashed when accessing AOL mail through IMAP. Lightning for 64 bit was also not working with the latest updates. Upgrading that was the best thing I ever did. It might help to go to Thunderbird 3.1 and/or a new version of Seamonkey if Eclipse is using any of their shared objects. Just a thought.

Thunderbird 3.0.5 was so bad I considered switching back to Kmail. It was always a good email client.

Sounds like You offer treat headache by cutting head (:

Thank You. I`ll try it. Last uptime of my workstation is 125 days with any crashes of Eclipse of any. But this was XP.

To me removing eclipse sounds more like cutting head and replacing it with something better :)

Since you are indicating you might try Netbeans, I thought I would add a couple of other things...

Netbeans has a different workflow and I can't tell you how painful it is to not know where menu items are. I understand this. Most people I work with use Eclipse and some are using it on Linux with success. One uses Eclipse on Fedora, one on Linux Mint, and another on Ubuntu. I'm the only Slackware/Netbeans person.

That said... If you are doing development with an application server and your projects are several thousand files or you want to do Entity Bean generation (which Netbeans does very well) you may have to tweak JVM settings. There are some tweaks in the netbeans installation directory under etc/netbeans.conf. You should be able to configure for you needs from there. If you set everything really high, it will slow it down so only put in what you need for the task. No perfect, but that's the way it is with some of the really intense operations. An example of "intense" is it takes about 3 or 4 hours to generate 1600+ Entity Beans on our database of 1000+ tables.

Your story of 125 days up with Eclipse is the best I've ever heard by far. I'm simply sharing what I do and that I've had similar issues in the (distant) past. I've been using Netbeans steadily from version 5.5 and I think their upgrade process and features are solid in general. Much better than my years on Eclipse. But don't let me tell you what's best for you. Use what *works* best in your situation. If you have issues, post back and I'll be more than happy to help where ever I can.

Happy Coding!

Thanks a lot urgor. Removing libxpcom_core.so from /usr/lib/seamonkey worked for me too. Does anyone know why a file in the seamonkey installation would affect eclipse?