• Post Reply Bookmark Topic Watch Topic
  • New Topic

Doubleclick shortcut: Eclipse won't start  RSS feed

 
Francois Bourgault
Ranch Hand
Posts: 67
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I've installed Eclipse 3.0 on my Mandrake 9.1 system . Everything went fine a short cut on the desktop perfect but when I doubleclick the icon to start the app. it looks like it's starting (hour glass turning) but then I get the main screen and it hangs there. At the console level, it works, at the root level as well as at the user level. I can create a project and start using it. I use kde3.1 and jdk1.5 . I thought this might be the problem, but Eclipse works fine when I start it from the konsole. Is this a permission thing? I did a "chmod +x eclipse" but it didn't do any thing. Any ideas? thanks
 
Tim Holloway
Saloon Keeper
Posts: 18800
74
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm in a different environment (RedHat/Fedora + gnome), so I can't say if there are known problems with your setup, but it can take a considerable amount of time between the moment the splash screen appears and the eclipse IDE opens up. If you have less than 256MB of RAM or a processor slower than 600MHz, figure on maybe a couple of weeks. OK, maybe not THAT long, but it will feel like it.

I just bumped up to 1GB on an Athlon 1800XP+ because according to the system monitors, 512MB was causing serious paging when I had large projects and was debugging.

It's not that Eclipse is a pig, it's that ALL Java IDEs are pigs. The only one I've been able to be really productive in on lower-end equipment is Emacs with jde.
 
Stefan Wagner
Ranch Hand
Posts: 1923
Linux Postgres Database Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If that was the reason, Francois would have recognized the same amount of time by starting from the console - wouldn't he?

It might have to do something how applications are started on kde by clicking icons.
Using fluxbox without any icon I can't help here - beside recommending fluxbox .

Talking about performance: I saw CBuilder from Borland - a native c or c++ application I guess - and it's not starting faster.
I would like the startup-time of eclipse to be smaller, but after starting, it's reasonable fast on a 1.1 Ghz machine with 256 MB.
OK - debugging.
Did you see native GUI-Debuggers being faster?
[ December 21, 2004: Message edited by: Stefan Wagner ]
 
Tim Holloway
Saloon Keeper
Posts: 18800
74
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Stefan Wagner:
If that was the reason, Francois would have recognized the same amount of time by starting from the console - wouldn't he?

Ah well, like Mr. Magoo, I'm not actually blind, just often miss the obvious. Actually, I've had enough problems from the gnome desktop that I start eclipse from a command window myself.

Truthfully, I'm not impressed with either gnome or KDE as desktop managers. Basic Linux is straightforward, managed with text config files, usually having a name resembling the product and located in /etc.

Gnome gives me the impression of an attempt to recreate the Windows Reigstry, warts and all (and some days I feel the Registry is almost ALL wart). Complex directory structure, stuff splattered all over the place and NO DOCUMENTATION!!!

I'm less familiar with KDE. I think it's a little cleaner.


Talking about performance: I saw CBuilder from Borland - a native c or c++ application I guess - and it's not starting faster.
I would like the startup-time of eclipse to be smaller, but after starting, it's reasonable fast on a 1.1 Ghz machine with 256 MB.
OK - debugging.
Did you see native GUI-Debuggers being faster?
[/QUOTE[
Not sure what a "native GUI-debugger" is. In any event, it's the overall IDE framework - especially startup or mode (perspective) switching that crawls. The Debugger is just an extra trask to topple an already overburdened machine.

I came up with my recommended hardware lower limits way back in my Visual Cafe days. Later additions haven't really made it that much worse, as far as I've noticed. Eclipse has spent a lot of effort towards "just-in-time" resources so every plugin in the world won't want major chunks of your machine when it starts. The foot-dragging startup you see is what's left over AFTER the optimization.

Red Hat has taken Eclipse and done some tuning, but I don't know if the results work anywhere but on RH Enterprise Linux.
 
Stefan Wagner
Ranch Hand
Posts: 1923
Linux Postgres Database Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree full to gnome and registry.
When I saw a comment: 'like the windows registry' I started deleting instantly.

The whole concept of the registry is ill.

If you delete something, the registry would have liked to know about, it is starting to collect trash you never get rid of.
If something is broken in the registry, you have to reinstall from scratch.
How can someone come to the idea of emulating that?

'native debugger' should have meant 'Debugger for c/ c++'.

After all: Buying a lot of RAM has never been a fault for me.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!