I think it was stated previously in this thread. The problem isn't Eclipse. The problem is the Android plugin. I'm using Eclipse more than 8h per day at work, and I don't have any problems there (I'm not doing any Android development at work). I can also use Eclipse at home without any problems if I never switch to the design view, or edit Android xml files. Switching to design view or editing xml files means that my Eclipse (tested several different versions) craches within one hour. Often several times per hour, and it's always a related to a memory problem, and it's due to leaking handles. Looks like it's either directly related to editing, or generation of R.
(And I'm having a 64 bit machine with 8 GB of RAM) On 4 Aug, 13:46, "Jonas Petersson" <jonas.peters...@xms.se> wrote: > Ah, I think I can relate to that statement: for 95+% of the XML editing > I referred to I used Eclipse itself, but like Kostya I stayed mostly in > the XML view, only an occasional glance at the graphical layout since > (at least for my cases) I decided the visual layout could not really be > trusted. Showing it in the emulator was the only way to know that it > actually worked as expected (yes, I had a rather picky spec to follow > and in a few cases I actually pulled out emacs for significant > restructuring, so I may have accidentally been lucky to manage for a week). > > Best / Jonas > > On 08/04/2010 11:55 AM, Kostya Vasilyev wrote: > > > > > This looks likely. > > > I can run Eclipse all day on a 4G Windows 64bit machine, but I edit my > > layouts "by hand", without the visual editor. > > > 04.08.2010 11:00, Mystique пишет: > >> I think there's some memory leak issue if editing XML files. > >> I realise if I only open .java it is ok. > >> So maybe a temp work around is to edit xml file with editor and open > >> only .java in eclipse? > > >> On Aug 4, 10:17 am, Doug<beafd...@gmail.com> wrote: > >>> The issue isn't what else is running on the computer. The issue is > >>> that Eclipse gets into an unrecoverable state where it lags horribly > >>> when switching between editors, at least on OSX. I can typically go 5 > >>> or 6 hours of steady use (more with intermittent use) until that state > >>> kicks in for me (MacBook Pro, 4GB, 2.4GHz Core 2 Duo). Quitting other > >>> apps at that point doesn't make any difference. The resource leak > >>> explanation is the only one that makes sense given my observations, > >>> which are daily since I do this to pay my mortgage. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
