That's clear.
--
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 op
What's wrong with my orientation attribute?
In the original App I use one layout for landscape and one for portrait.
But that should have nothing todo with that error anyway...
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this
Have u ever thought to fix ur orientation attribute?
On Jun 30, 2011 7:38 AM, "Atlan" wrote:
> I am really total desperate. Since a week I am searching a memory leak in
my
> App.
> I reduced everything to that little Activity attached.
>
> The problem *occurres** **if the orientation changes. For
>
> Just to be clear, what are the precise bounds of "the debugger attached"?
>
> Or, to phrase it another way, which of the following should be avoided:
>
> -- Actively debugging in Eclipse (Debug As...)
>
This one, since it involves the debugger.
> -- Running the project from Eclipse (Run As..
On Thu, Jun 30, 2011 at 3:23 AM, Romain Guy wrote:
> Checking the heap dump is perfectly, just make sure you're not doing it with
> the debugger attached.
Just to be clear, what are the precise bounds of "the debugger attached"?
Or, to phrase it another way, which of the following should be avoi
OK + Thank you. I linked this conversation to my post in Stack Overflow.
Hope it helps some others too.
Also make sure to force a GC a couple of times on your process before taking
> a heap dump.
>
That's what I made.
Mike
--
You received this message because you are subscribed to the Googl
Checking the heap dump is perfectly, just make sure you're not doing it with
the debugger attached. Also make sure to force a GC a couple of times on
your process before taking a heap dump.
On Thu, Jun 30, 2011 at 12:19 AM, Atlan wrote:
> That's what I learn in this conversation.
>
> But as said
That's what I learn in this conversation.
But as said before I made a heap dump because my app crashed after changing
the
orientation in the emulator for about 6 to 10 times. This caused me to check
the heap and because I found no problem in my code I started to make heap
dumps.
The dumps sho
A system which shows me different results depending on how I observe it is a
bit like "quantum physics".
Until the last few weeks I was really impressed about Android, it's API an
how Google brought all these things together but after searching a memory
leak for about 2 weeks which only exists
I actually never ever do a heap dump with the debugger attached. You really
want to make sure there's no external entity interacting with your heap.
On Wed, Jun 29, 2011 at 11:39 PM, Atlan wrote:
> Hi Romain, thanks for answering this post. I think I read all your blog
> posts according to this
Its so less complicated than 'quantum physics'
--
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+unsubsc
Hi Romain, thanks for answering this post. I think I read all your blog
posts according to this subject...
Maybe it's clear for you that this behavior is normal but it was at least
not clear for me.
I also think that a lot of other people are suffering with that. In all the
posts I read it was
Grr.
--
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, vi
Debuggers usually keep objects alive, preventing them from being freed.
On Wed, Jun 29, 2011 at 11:09 PM, Chris wrote:
> You think debugging should come for free or something?
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To po
You think debugging should come for free or something?
--
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
It drives me nuts - that only happens if I am debugging. If I do a "normal"
Run all the Activities are gone.
To me thats a big Bug in the development system!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email
On Wed, Jun 29, 2011 at 4:58 PM, Atlan wrote:
> I am really total desperate. Since a week I am searching a memory leak in my
> App.
You have not demonstrated that you have a memory leak in your app.
> I reduced everything to that little Activity attached.
> The problem occurres if the orientatio
I am really total desperate. Since a week I am searching a memory leak in my
App.
I reduced everything to that little Activity attached.
The problem *occurres** **if the orientation changes. For example if I
change the orientation in the emulator 6 times I have 6 Instances of my *
*Activity in M
18 matches
Mail list logo
