Try to dynamically create the ImaveView. The snippet code is listed
below. It's not the solution just a hint. For testing you can call
also System.gc() after setContentView(new View(this)); But using it in
your code is not a good way. Read this
http://blog.javia.org/android-allocation-free-code-avo
In onStop method I am trying to remove all references to my view hierarchy
so garbage collector to reclaim the memory of layout. Setting content view
to null throws Exception so I set contentView to something that doesn't use
much memory, while the activity is not visible.
--
You received this
@Override
protected void onStop() {
super.onStop();
setContentView(new View(this));
}
What exactly are you trying to do here?
On Jun 21, 1:37 pm, mladen wrote:
> Hello,
> I am trying to optimize the memory usage of my application on Xoom. I
> h
I used to know how to do this but I forgot.
(Uh, maybe you could tell us what you mean by "memory problem"? At
least hint at a few symptoms?)
On Dec 27, 7:15 am, Ramesh Solanki wrote:
> i have developed an application that working perfectly
> but sometimes it causes error i thing that is memoy
If you can see an object it's not garbage.
On Sep 1, 8:48 am, Shashidhar wrote:
> Hi,
> In my application I change layouts very frequently with most of the user
> interactions. Each time when a new layout is drawn, the applications memory
> size is increasing. I can see this in DDMS.
> This is
It wasn't solved, now it ask for less memory but still outOfMemory
sometimes. I really don't know what to do if anyone knows how to
solve it, please tell me!!!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send
thx for your time Marc! but I already solve it =)
I have seen a lot of people has this error or something like this, but
no answer... and i was lucky...
I just put the "big" image in the RAW directory... because the problem
appears to be that when i start the app again, this "big" image was
transfo
Hi Kofa,
I guess you have a memory leak here. Please make sure that all your
data is cleaned up, i.e. no hard references are left.
Try to call the GC manually and see how much it cleans up.
Tip: Override the finalize() method of your activity and print out a
log message there to see if the activi
I forgot to say that the activity with the problem has an imageview
that loads a PNG of 621Kb and a bunch of imageviews.
--
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.co
Note that your code is not synchronized and may cause problems.
Your stopThread method sets blinker to null and stopThread is probably
called by the UI thread.
The 'run' method runs in the other thread and reads the value of
'blinker'.
Since you haven't synchronized the writing and reading of 'b
Thank you so much! You led me right to the problem. I was using code I
found on Sun's website on how to start and stop threads and it was
creating a second thread every time it ran.
I want to post the solution in case anyone else has this issue.
This is what I started with.
blinker makes a new th
On Mar 4, 1:02 pm, Joshua Frank wrote:
> I have a couple of worker threads in my app which I stop and restart
> during onPause() and onResume(). I use a method that clears all the
> reference to and from the threads when stopping. However ThreadGroup
> is still retaining a reference to my threads
I have checked the memory used, I can't see any problem;
All my cursor are closed after being used.
In addition, the last log file I receive show me that this problem
arrived the fifth time the application tryed to use the media
provider.
Is anyone from Google who could give an hilight about this
It doesn't do anything but draw the bitmap. A standard BitmapDrawable
has other features (gravity, alpha, etc.)
On Thu, Aug 6, 2009 at 4:05 AM, for android wrote:
> How is the FasterBitMapDrawable in the Shelves different from normal
> BitmapDrawable?
>
> On Thu, Aug 6, 2009 at 2:38 PM, peter wr
How is the FasterBitMapDrawable in the Shelves different from normal
BitmapDrawable?
On Thu, Aug 6, 2009 at 2:38 PM, peter wrote:
>
> Create a Bitmap is very consume memory
>
> On Aug 6, 2:41 pm, Rahul wrote:
> > Hi all
> >
> > i have one big problem in android due to this my application crashe
Create a Bitmap is very consume memory
On Aug 6, 2:41 pm, Rahul wrote:
> Hi all
>
> i have one big problem in android due to this my application crashesh
> every time
>
> My Problem are
>
> 1. Bitmap memory exceed error
> 2. Out of memory error
>
> somebody pls help me to solve this problem.
>
>
Either your application is leaking memory or you are just using too
much memory. Use less memory.
On Wed, Aug 5, 2009 at 11:41 PM, Rahul wrote:
>
> Hi all
>
> i have one big problem in android due to this my application crashesh
> every time
>
> My Problem are
>
> 1. Bitmap memory exceed error
>
17 matches
Mail list logo
