Marcelo,
The slowdown you are seeing (by a factor of two or so), is what I'm
seeing too, with Eclipse on Windows 7/64, and it's about the same with
several very different phones.
It seems typical, and I've learned to live with it.
Others reported more significant slowdowns in certain cases (
Eric's inappropriate manner notwithstanding, I'll weigh in with him
and Leigh to say that, yes, there can be a genuine and substantial
slowdown when running under the debugger.
I am using Eclipse Classic 3.6.2 with the latest ADK (downloaded two
days ago via the standard mechanisms). For hardware,
I use IDEA on both Windows and Linux and have absolutely no problems.
I much prefer it to Eclipse because of my .NET and ReSharper
background.
On Apr 15, 1:17 pm, TreKing wrote:
> On Fri, Apr 15, 2011 at 11:39 AM, Eric wrote:
> > What does Eclipse vs. IDEA have to do with any of this?
>
> You me
Have you tried my suggestion from early on in the thread: profile your app when
the debugger is attached to see where the slowdown is? Bonus points for
comparing it to a profile without the debugger.
If you need help with the profiler, start here:
http://android-developers.blogspot.com/2010/10/
I agree with you about the *simulator/emulator*. If you don't have an
absolute stellar system (and even then...), the emulator can be very slow.
But Eric's problem is with an actual device, not the emulator and Google is
acknowledging the problem with the emulator.
And I haven't seen the issues
Fair enough. I'm just saying. I will put up a sample when the lone in
Lone Dwarf Games Inc becomes many, but for now I just can't.
On 4/15/2011 3:01 PM, Mark Murphy wrote:
On Fri, Apr 15, 2011 at 2:55 PM, Leigh McRae
wrote:
This problem has been brought up before and I know at least one
On Fri, Apr 15, 2011 at 2:55 PM, Leigh McRae
wrote:
> This problem has been brought up before and I know at least one other person
> on this list has mentioned it. I just did a test and my game takes 35
> seconds to load to the main menu when launched from eclipse using a
> simulator. When I deb
This problem has been brought up before and I know at least one other
person on this list has mentioned it. I just did a test and my game
takes 35 seconds to load to the main menu when launched from eclipse
using a simulator. When I debug using a simulator with no break points
at all, it take
I hear you brother!
On Fri, Apr 15, 2011 at 1:41 PM, Eric wrote:
>
>
> On Apr 15, 1:23 pm, Mark Murphy wrote:
> > > I do not have any
> > > watches or breakpoints activated.
> >
> > Just because *you* don't have anything like that activated does not
> > mean that the *IDE* is not doing somethin
On Apr 15, 12:47 pm, Streets Of Boston
wrote:
> At what point does your app start running slowly:
> - Initially, don't start DDMS or Jetbrain or Eclipse.
> - Run the app on your phone which is unconnected. Does it run OK or slow?
> - Then connect your phone to your Mac through USB: Does the app
Great, we'll make sure to tell Google about this one. Thanks!
Kris
On Fri, Apr 15, 2011 at 1:52 PM, Eric wrote:
>
>
> On Apr 15, 1:46 pm, TreKing wrote:
> > On Fri, Apr 15, 2011 at 12:40 PM, Eric wrote:
> > > In any event, since absolutely nobody else seems to experience a
> debugging
> > > s
On Apr 15, 1:46 pm, TreKing wrote:
> On Fri, Apr 15, 2011 at 12:40 PM, Eric wrote:
> > In any event, since absolutely nobody else seems to experience a debugging
> > situation that is painfully slow, I will have to unfortunately assume that
> > some aspect of my application (i.e. high level of
On Fri, Apr 15, 2011 at 12:40 PM, Eric wrote:
> In any event, since absolutely nobody else seems to experience a debugging
> situation that is painfully slow, I will have to unfortunately assume that
> some aspect of my application (i.e. high level of network traffic, and
> high level of UI updat
On Apr 15, 1:23 pm, Mark Murphy wrote:
> > I do not have any
> > watches or breakpoints activated.
>
> Just because *you* don't have anything like that activated does not
> mean that the *IDE* is not doing something that might use debugging
> interfaces that might be slowing things down. Clearly
On Fri, Apr 15, 2011 at 12:39 PM, Eric wrote:
> What does Eclipse vs. IDEA have to do with any of
> this?
Debugging, apparently. Personally, I use neither of them much.
> I do not have any
> watches or breakpoints activated.
Just because *you* don't have anything like that activated does not
me
On Fri, Apr 15, 2011 at 11:39 AM, Eric wrote:
> What does Eclipse vs. IDEA have to do with any of this?
>
You mean besides the fact that all of using Eclipse have no problem and you,
the lone person using IDEA, are?
---
At what point does your app start running slowly:
- Initially, don't start DDMS or Jetbrain or Eclipse.
- Run the app on your phone which is unconnected. Does it run OK or slow?
- Then connect your phone to your Mac through USB: Does the app still run
OK?
- Then start DDMS (not Jetbrain or Eclipse
On Apr 15, 12:11 pm, Mark Murphy wrote:
> When you contacted your IDE vendor (Jetbrains) regarding your problem
> with their product, what did they tell you?
> When you tested your application in Eclipse -- to prove that the
> problem is in Google's code and not Jetbrains' -- what did you find
On Apr 15, 11:48 am, Kristopher Micinski
wrote:
> However, insulting Google makes you look unintelligible (I'm guessing that
> calling it a "simulator" doesn't win many points either.)
I never called the debugger a simulator. Maybe I should have never
called the painful emulator a simulator, t
On Apr 15, 11:37 am, Streets Of Boston
wrote:
> In my experience, apps run somewhat slower in the debugger, but not by much.
> It is certainly not 'utterly unusable' slow.
> If you do experience a very very slow performance while debugging, it may
> help us answer or solve your problem to descri
On Fri, Apr 15, 2011 at 11:53 AM, Eric wrote:
> Ok, I can supply some info, but I don't think it will help. The
> problem is with the debugger, not my setup. That is why my post was
> terse, prompting Google to get their act together.
And as soon as you demonstrate proof that Google's the sourc
On Fri, Apr 15, 2011 at 10:53 AM, Eric wrote:
> Ok, I can supply some info, but I don't think it will help.
>
Better more information than not enough, usually.
> That is why my post was terse, prompting Google to get their act together.
>
I don't think this is going to prompt Google to do any
The one main difference between my setup and yours is that your use
Jetbrains. I'm using Eclipse 3.6. Have you tried using Eclipse?
What is your performance if you just fire up 'ddms' (not Jetbrains or any
other IDE) and dump the heap or take a look at your apps' threads?
--
You received this m
On Fri, Apr 15, 2011 at 10:20 AM, Eric wrote:
> What else do you want to know??
>
To quote myself: "... all the relevant variables (OS, Eclipse version, ADT
version, any logs, etc, etc)".
> When I run it outside the debugger, it performs satisfactorily. The only
> changing variable is the deb
On Fri, Apr 15, 2011 at 11:20 AM, Eric wrote:
>
> On Apr 14, 11:22 pm, TreKing wrote:
> > I have a Nexus One with 2.3.3 installed as well and it runs just fine for
> > me.
> > A very real possibility is that the "complete crap environment" is your
> own.
> > It would be hard to tell, though, fro
In my experience, apps run somewhat slower in the debugger, but not by much.
It is certainly not 'utterly unusable' slow.
If you do experience a very very slow performance while debugging, it may
help us answer or solve your problem to describe what your setup is. Maybe
some issue in the USB com
On Apr 15, 3:05 am, String wrote:
> Sure, apps run slower when attached to the debugger, but that's hardly
> surprising given the overhead.
The iOS version of my app performs no slower in the debugger than it
does outside the debugger.
--
You received this message because you are subscribed t
On Apr 14, 11:22 pm, TreKing wrote:
> I have a Nexus One with 2.3.3 installed as well and it runs just fine for
> me.
> A very real possibility is that the "complete crap environment" is your own.
> It would be hard to tell, though, from the complete lack of information in
> your post. "It's slow
same here. Absolutely no problems Nexus One 2.3.3, even in debug mode.
--
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
an
Sure, apps run slower when attached to the debugger, but that's hardly
surprising given the overhead.
I have noticed that one of my apps seems to slow down more than the others,
which leads me to believe that certain operations are more affected than
others. It's never been problematic enough f
My Nexus One 2.3.3 has NO speed issues with debuggiing.
On Apr 15, 11:01 am, Eric wrote:
> When I run my app in the debugger, via a USB cable, it is completely
> and utterly unusably slow. I have 2.3.3 installed on my NexusOne.
> How does Google expect us to work with a complete crap environment
31 matches
Mail list logo
