Android 4.0.3 for Galaxy Tab 10.1 provides a native task manager that shows
the memory used by the app.
Only when I call GC after list.Clear() explicitly memory usage is stable.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Memory-Leak-With-Simple-App-tp5713078
On Apr 1, 2013, at 7:51 PM, Natanael wrote:
> I have a simple app that calls a method in the click event of the button.
>
> As I'm clicking the button the use of memory is increasing and it is not
> released.
How are you tracking memory use? Which memory is constantly increasing and
isn't rele
On Apr 2, 2013, at 10:14 AM, Paul Johnson wrote:
> Without seeing some code
He provided code. The problem is that he provided it via the @#%$ nabble.com
web interface, which has this Q#$@#$% tendency to STRIP all attachments/etc.
before sending it to the list.
TL;DR: you need to visit here to
Hi,
I suspect this problem is related to the use of List. The Clear() method
seems not release the memory.
Without seeing some code, it's hard to say what the problem is. I've not
seen any problems with List within a click event as once the event is
out of scope, the object is destroyed.
P
Found my memory leak.
It came from Sqlite Cursors not being closed. I discovered that when using
Sqlite Cursors you should always use the following construct:
ICursor C = SomeFunction();
using( C )
{
try
{
...
...
Do Something with the Cursor
imho webrequest sucks here. use the native java and see if you have the
same problem.
Also, memory leaks might be related to your code. Are you properly using
usings? Have you considered scope? The GC is pretty smart unless you have
bad scoping...
Also how are you cleaning up your references ? If
Hi Terry,
If I were you, I would deactivate one component of suspicion (or replace
it with dummy code) and look if the problem goes away or persists.
-- Henon
On 18.07.2012 03:41, Terry151151 wrote:
> I have a program that uses WebRequest and Sqlite. I sends request to the
> server and then update
Thanks, that did solve the problem. I also added another GC.Collect() in my
OnRestart() override, just to be absolutely sure.
Cheers, Andreas.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Memory-Leak-with-Background-Image-tp5165833p5430759.html
Sent from the Mon
On Jan 23, 2012, at 6:19 AM, subsembly wrote:
> it seems that bitmap images attached as background drawables are never
> released.
They're released, they're just not released soon enough. Hopefully this will
provide some background and clarification:
http://docs.xamarin.com/android/adv
