Comments on: Eclipse + OS X = unhappy http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/ Ramblings on Java, Wicket, cats and other stuff Fri, 29 Aug 2008 03:43:01 +0000 http://wordpress.org/?v=2.5.1 By: Tim Michalski http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56960 Tim Michalski Wed, 11 Jun 2008 22:00:49 +0000 http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56960 Xcode?? That takes up way too much memory. Why not just use vi or emacs on the terminal for coding. In fact, it would really help if you disabled the Mac OSX user interface and just booted into the console. You'd probably not have any more IDE issues then. ;) I'm having the same issues and figured that I would just put a hammer through my monitor. The JVM & Kernel quickly stopped bickering and started bi-lateral communications with all parties involved. Xcode?? That takes up way too much memory. Why not just use vi or emacs on the terminal for coding. In fact, it would really help if you disabled the Mac OSX user interface and just booted into the console. You’d probably not have any more IDE issues then. ;)

I’m having the same issues and figured that I would just put a hammer through my monitor. The JVM & Kernel quickly stopped bickering and started bi-lateral communications with all parties involved.

]]> By: Matthew Peterson http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56935 Matthew Peterson Fri, 06 Jun 2008 03:36:44 +0000 http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56935 Just use Xcode or any editor that does syntax highlighting instead of wasting time with an IDE......then you can allocate that RAM to JVM instead of to the IDE Just use Xcode or any editor that does syntax highlighting instead of wasting time with an IDE……then you can allocate that RAM to JVM instead of to the IDE

]]> By: srecko toroman http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56897 srecko toroman Thu, 22 May 2008 23:08:14 +0000 http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56897 Well it only happens with Eclipse 3.3 Enterprise Edition on Unix platforms. For example Classic eclipse (*without some plugins e.g. mylyn*) has never crashed on my Debian. Anyway, Eclipse is just great for being a powerful platform, SWT is great too, but it is not quite perfect, yet :) Well it only happens with Eclipse 3.3 Enterprise Edition on Unix platforms. For example Classic eclipse (*without some plugins e.g. mylyn*) has never crashed on my Debian.

Anyway, Eclipse is just great for being a powerful platform, SWT is great too, but it is not quite perfect, yet :)

]]> By: Harald Walker http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56862 Harald Walker Fri, 16 May 2008 23:15:44 +0000 http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56862 How much RAM does your Mac have? For over a year I had 2 GB and most of the time it went very well with Mac OS X (first Tiger, then Leopard) and Eclipse (3.3.2, 3.3.3). When I started running multiple Eclipse instances next to each other plus Oracle XE on a Linux VM and the usual other programs (Firefox, Thunderbird,...) things started to get unbearable slow. I've since the upgraded the hard disk in my MacBook Pro to a 7200 rpm drive and added another 2GB of memory. That helped a lot and everything is running fine. I've never had problems with crashing Eclipse (except when a memory module was defect). How much RAM does your Mac have? For over a year I had 2 GB and most of the time it went very well with Mac OS X (first Tiger, then Leopard) and Eclipse (3.3.2, 3.3.3). When I started running multiple Eclipse instances next to each other plus Oracle XE on a Linux VM and the usual other programs (Firefox, Thunderbird,…) things started to get unbearable slow. I’ve since the upgraded the hard disk in my MacBook Pro to a 7200 rpm drive and added another 2GB of memory. That helped a lot and everything is running fine. I’ve never had problems with crashing Eclipse (except when a memory module was defect).

]]> By: Newton http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56707 Newton Tue, 06 May 2008 18:38:04 +0000 http://martijndashorst.com/blog/2008/04/03/eclipse-os-x-unhappy/#comment-56707 I have run Eclipse on OS X for years and the only problem I had was early on when SWT didn't play nice on OS X. My guess is that your machine is in general low on memory. Check your activity monitor with just a browser and see how much memory you have available. My guess is that it is pretty low. Leopard takes a lot of memory by itself and all those cool desktop widgets eat even more even when they aren't being displayed. I have 1gig on my current machine which was plenty under 10.4 but I am going to add another gig with Leopard. Luckily memory is cheap. I have run Eclipse on OS X for years and the only problem I had was early on when SWT didn’t play nice on OS X. My guess is that your machine is in general low on memory. Check your activity monitor with just a browser and see how much memory you have available. My guess is that it is pretty low. Leopard takes a lot of memory by itself and all those cool desktop widgets eat even more even when they aren’t being displayed. I have 1gig on my current machine which was plenty under 10.4 but I am going to add another gig with Leopard. Luckily memory is cheap.

]]>