Re: [android-developers] Every few hours Eclipse + ADT runs out of resources...

2012-06-18 Thread Nobu Games
Hi

I know this is an old post but I'm running across the very same problem 
with Eclipse every single day since I installed the latest SDK / plugin 
version. After about 3 to 4 hours of coding and debugging (on an actual 
device) the run process (for installing and starting the app) gets slower 
and slower up to a point where the progress indicator in the status bar 
does not move at all and Eclipse gets unresponsive.

After waiting for a few minutes I may get an OutOfMemoryException. But 
usually I have to kill the Eclipse process which usually damages workspace 
settings and sometimes even a few opened files.

I am using:

Eclipse Version: 3.7.2
Build id: M20120208-0800

OS: OpenSUSE 12.1

Java VM: java-1.7.0-sun (for running Eclipse itself)

ADT Plugin:18.0.0.v201203301601-306762   

Android SDK Tools: Rev 19
Android SDK Platform Tools: Rev 11

Unfortunately I cannot provide you with relevant Eclipse error log excerpts 
because the log file got trashed after recovering from the last crash.

I'm not sure how helpful that is. But it takes me by surprise that I 
couldn't find any more recent complaints / posts about this issue, so maybe 
it is just me and my setup. However, I have only encountered these problems 
in relation with Android development and everything used to work without a 
problem so far.


Cheers,

Thomas

On Monday, September 13, 2010 2:15:37 AM UTC-5, Xavier Ducrohet wrote:

 in ADT 0.9.8, we've fixed a (big) memory leak happening in the layout
 editor. I suggest you update (0.9.8 was released on Wednesday).

 Let me know if this still happens.

 Xav

 On Sun, Sep 12, 2010 at 2:38 PM, mmo mmo...@gmail.com wrote:
  When I am developing for Android and repeatedly running and/or
  debugging an Android app in the emulator then about every two hours or
  so I get an Out-of-memory exception, occasionally also an out-of -
  resources- or out-of-GWT-handles exception. At that point one can only
  stop and restart eclipse. Apparently the ADK must be doing something
  wrong, because I have been developing with Eclipse now for 5+ years
  and I normally never see this. ADT is a really the exception here.
  Is there any setting or patch that helps top avoid this? I have
  already given it more heap space (750M) to stretch the time between
  these hickups a bit, but that approach isn't really sustainable.
 
  This is using Eclipse 3.5 (Galileo) and the Android SDK r06 running a
  FroYo AVD.
 
  Michael
 
  --
  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
 

 -- 
 Xavier Ducrohet
 Android SDK Tech Lead
 Google Inc.

 Please do not send me questions directly. Thanks!



-- 
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

Re: [android-developers] Every few hours Eclipse + ADT runs out of resources...

2012-06-18 Thread Tor Norbye
Can you try using ADT 20 Preview 3?   It contains various leak fixes, such
as http://code.google.com/p/android/issues/detail?id=26774 .

-- Tor

On Thu, Jun 14, 2012 at 11:35 AM, Nobu Games dev.nobu.ga...@gmail.comwrote:

 Hi

 I know this is an old post but I'm running across the very same problem
 with Eclipse every single day since I installed the latest SDK / plugin
 version. After about 3 to 4 hours of coding and debugging (on an actual
 device) the run process (for installing and starting the app) gets slower
 and slower up to a point where the progress indicator in the status bar
 does not move at all and Eclipse gets unresponsive.

 After waiting for a few minutes I may get an OutOfMemoryException. But
 usually I have to kill the Eclipse process which usually damages workspace
 settings and sometimes even a few opened files.

 I am using:

 Eclipse Version: 3.7.2
 Build id: M20120208-0800

 OS: OpenSUSE 12.1

 Java VM: java-1.7.0-sun (for running Eclipse itself)

 ADT Plugin:18.0.0.v201203301601-306762

 Android SDK Tools: Rev 19
 Android SDK Platform Tools: Rev 11

 Unfortunately I cannot provide you with relevant Eclipse error log
 excerpts because the log file got trashed after recovering from the last
 crash.

 I'm not sure how helpful that is. But it takes me by surprise that I
 couldn't find any more recent complaints / posts about this issue, so maybe
 it is just me and my setup. However, I have only encountered these problems
 in relation with Android development and everything used to work without a
 problem so far.


 Cheers,

 Thomas

 On Monday, September 13, 2010 2:15:37 AM UTC-5, Xavier Ducrohet wrote:

 in ADT 0.9.8, we've fixed a (big) memory leak happening in the layout
 editor. I suggest you update (0.9.8 was released on Wednesday).

 Let me know if this still happens.

 Xav

 On Sun, Sep 12, 2010 at 2:38 PM, mmo mmo...@gmail.com wrote:
  When I am developing for Android and repeatedly running and/or
  debugging an Android app in the emulator then about every two hours or
  so I get an Out-of-memory exception, occasionally also an out-of -
  resources- or out-of-GWT-handles exception. At that point one can only
  stop and restart eclipse. Apparently the ADK must be doing something
  wrong, because I have been developing with Eclipse now for 5+ years
  and I normally never see this. ADT is a really the exception here.
  Is there any setting or patch that helps top avoid this? I have
  already given it more heap space (750M) to stretch the time between
  these hickups a bit, but that approach isn't really sustainable.
 
  This is using Eclipse 3.5 (Galileo) and the Android SDK r06 running a
  FroYo AVD.
 
  Michael
 
  --
  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 android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+**unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
  For more options, visit this group at
  http://groups.google.com/**group/android-developers?hl=enhttp://groups.google.com/group/android-developers?hl=en
 

 --
 Xavier Ducrohet
 Android SDK Tech Lead
 Google Inc.

 Please do not send me questions directly. Thanks!

  --
 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

-- 
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

Re: [android-developers] Every few hours Eclipse + ADT runs out of resources...

2012-06-18 Thread Tor Norbye
By the way, ADT 20 Preview 3 is here:
http://tools.android.com/download/adt-20-preview . We'll hopefully have a
final build in the next few weeks.

-- Tor

On Mon, Jun 18, 2012 at 7:34 AM, Tor Norbye tnor...@google.com wrote:

 Can you try using ADT 20 Preview 3?   It contains various leak fixes, such
 as http://code.google.com/p/android/issues/detail?id=26774 .

 -- Tor


 On Thu, Jun 14, 2012 at 11:35 AM, Nobu Games dev.nobu.ga...@gmail.comwrote:

 Hi

 I know this is an old post but I'm running across the very same problem
 with Eclipse every single day since I installed the latest SDK / plugin
 version. After about 3 to 4 hours of coding and debugging (on an actual
 device) the run process (for installing and starting the app) gets slower
 and slower up to a point where the progress indicator in the status bar
 does not move at all and Eclipse gets unresponsive.

 After waiting for a few minutes I may get an OutOfMemoryException. But
 usually I have to kill the Eclipse process which usually damages workspace
 settings and sometimes even a few opened files.

 I am using:

 Eclipse Version: 3.7.2
 Build id: M20120208-0800

 OS: OpenSUSE 12.1

 Java VM: java-1.7.0-sun (for running Eclipse itself)

 ADT Plugin:18.0.0.v201203301601-306762

 Android SDK Tools: Rev 19
 Android SDK Platform Tools: Rev 11

 Unfortunately I cannot provide you with relevant Eclipse error log
 excerpts because the log file got trashed after recovering from the last
 crash.

 I'm not sure how helpful that is. But it takes me by surprise that I
 couldn't find any more recent complaints / posts about this issue, so maybe
 it is just me and my setup. However, I have only encountered these problems
 in relation with Android development and everything used to work without a
 problem so far.


 Cheers,

 Thomas

 On Monday, September 13, 2010 2:15:37 AM UTC-5, Xavier Ducrohet wrote:

 in ADT 0.9.8, we've fixed a (big) memory leak happening in the layout
 editor. I suggest you update (0.9.8 was released on Wednesday).

 Let me know if this still happens.

 Xav

 On Sun, Sep 12, 2010 at 2:38 PM, mmo mmo...@gmail.com wrote:
  When I am developing for Android and repeatedly running and/or
  debugging an Android app in the emulator then about every two hours or
  so I get an Out-of-memory exception, occasionally also an out-of -
  resources- or out-of-GWT-handles exception. At that point one can only
  stop and restart eclipse. Apparently the ADK must be doing something
  wrong, because I have been developing with Eclipse now for 5+ years
  and I normally never see this. ADT is a really the exception here.
  Is there any setting or patch that helps top avoid this? I have
  already given it more heap space (750M) to stretch the time between
  these hickups a bit, but that approach isn't really sustainable.
 
  This is using Eclipse 3.5 (Galileo) and the Android SDK r06 running a
  FroYo AVD.
 
  Michael
 
  --
  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 android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+**unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
  For more options, visit this group at
  http://groups.google.com/**group/android-developers?hl=enhttp://groups.google.com/group/android-developers?hl=en
 

 --
 Xavier Ducrohet
 Android SDK Tech Lead
 Google Inc.

 Please do not send me questions directly. Thanks!

  --
 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




-- 
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

Re: [android-developers] Every few hours Eclipse + ADT runs out of resources...

2010-09-13 Thread Xavier Ducrohet
in ADT 0.9.8, we've fixed a (big) memory leak happening in the layout
editor. I suggest you update (0.9.8 was released on Wednesday).

Let me know if this still happens.

Xav

On Sun, Sep 12, 2010 at 2:38 PM, mmo mmo...@gmail.com wrote:
 When I am developing for Android and repeatedly running and/or
 debugging an Android app in the emulator then about every two hours or
 so I get an Out-of-memory exception, occasionally also an out-of -
 resources- or out-of-GWT-handles exception. At that point one can only
 stop and restart eclipse. Apparently the ADK must be doing something
 wrong, because I have been developing with Eclipse now for 5+ years
 and I normally never see this. ADT is a really the exception here.
 Is there any setting or patch that helps top avoid this? I have
 already given it more heap space (750M) to stretch the time between
 these hickups a bit, but that approach isn't really sustainable.

 This is using Eclipse 3.5 (Galileo) and the Android SDK r06 running a
 FroYo AVD.

 Michael

 --
 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




-- 
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.

Please do not send me questions directly. Thanks!

-- 
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


[android-developers] Every few hours Eclipse + ADT runs out of resources...

2010-09-12 Thread mmo
When I am developing for Android and repeatedly running and/or
debugging an Android app in the emulator then about every two hours or
so I get an Out-of-memory exception, occasionally also an out-of -
resources- or out-of-GWT-handles exception. At that point one can only
stop and restart eclipse. Apparently the ADK must be doing something
wrong, because I have been developing with Eclipse now for 5+ years
and I normally never see this. ADT is a really the exception here.
Is there any setting or patch that helps top avoid this? I have
already given it more heap space (750M) to stretch the time between
these hickups a bit, but that approach isn't really sustainable.

This is using Eclipse 3.5 (Galileo) and the Android SDK r06 running a
FroYo AVD.

Michael

-- 
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