Re: [mono-android] Simple project with massive memory leak

2011-11-28 Thread Jonathan Pryor
On Nov 27, 2011, at 4:34 PM, Axel Busch wrote: > Hi Jon. I don't remember how high the count went. If you think it's valuable > at this time, I can run the code on a few different devices and android > versions. I would suggest just waiting for the next release, and retrying your fuller tests.

Re: [mono-android] Simple project with massive memory leak

2011-11-27 Thread Axel Busch
On 27.11.11 12:53, Jonathan Pryor wrote: > Do you remember at what count it was crashing at for you? > > If I modify the sample to perform a GC.Collect() after the `client.Dispose()` > call (Activity1.cs:66), then memory use seems far more stable, staying at > ~33.5MB by the same 520 iteration co

Re: [mono-android] Simple project with massive memory leak

2011-11-27 Thread Jonathan Pryor
On Nov 21, 2011, at 1:09 PM, Jack Bond wrote: > The project I've attached has a single activity that does a single web > service call, but it leaks memory massively on my wifi galaxy tablet and > galaxy S II phone. Could you or Axel Busch provide more information, e.g. how high the count gets bef

Re: [mono-android] Simple project with massive memory leak

2011-11-27 Thread Miguel de Icaza
Hello, The project I've attached has a single activity that does a single web > service call, but it leaks memory massively on my wifi galaxy tablet and > galaxy S II phone. They are both up to date with the latest software. Can > someone be kind enough to compile/run this project and confirm that

Re: [mono-android] Simple project with massive memory leak

2011-11-27 Thread Sayed Arian Kooshesh
ican indian, oriental, or a mix of >>> everything. All ppl deserve equal rights. Please think first on peace and >>> avoid war. >>> Everyone has the right to make mistakes, to learn, to teach and to be >>> taught. No one is the cente

Re: [mono-android] Simple project with massive memory leak

2011-11-27 Thread Sayed Arian Kooshesh
. Please think first on peace and >> avoid war. >> Everyone has the right to make mistakes, to learn, to teach and to be >> taught. No one is the center of the Universe. >> Thanks, >> Karl >> From: Sayed Arian Kooshesh >> Reply-To: "monodroid@lists.xi

Re: [mono-android] Simple project with massive memory leak

2011-11-27 Thread Fabrice
hanks, > > Karl > > From: Sayed Arian Kooshesh > Reply-To: "monodroid@lists.ximian.com" > Date: Sat, 26 Nov 2011 23:57:59 -0600 > To: "monodroid@lists.ximian.com" > Subject: Re: [mono-android] Simple project with massive memory leak > > Stop hiri

Re: [mono-android] Simple project with massive memory leak

2011-11-27 Thread Karl Heinz Brehme Arredondo
nter of the Universe. Thanks, Karl From: Sayed Arian Kooshesh Reply-To: "monodroid@lists.ximian.com" Date: Sat, 26 Nov 2011 23:57:59 -0600 To: "monodroid@lists.ximian.com" Subject: Re: [mono-android] Simple project with massive memor

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Agustin Gimenez
LOL... ¿seriously? ¿someone with that name can be so moron to say that? ROFL Also, let other people live what they like, seeing the code it's obvious for everyone that is not the code from a pro, but hey, every of us had to learn in some point of time, no? Instead opf saying nonsenses apport

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
you guys wanna know why I'm mad. Cuz this is real project that some guy hired what he though was a real programmer. In the end, they are gonna have to hire someone like me to go in and fix crap code. I can see crap code from a mile away. Stop hiring from outside the u.s. ___

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Agustin Gimenez
Sayed, when the DownloadString function (the main function for the thread) is finished, it's destroyed and the webclient is de-referenced, the only reference left is the one on the async call which is eliminated when the async call finishes, so, your im-so-good theroy is wrong WORNGGG!!! XD WevCli

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
If you didn't learn what i just said in your basic programming class. Quit. You are a failure. ___ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
here let me put this another way. you are creating a thread in a callback that creates another thread in it's call back. Basically, nothing goes out of scope, GC does nothing. Is tha tsimple enough for you non-programmers? ___ Monodroid mailing list Mono

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Agustin Gimenez
I agree that the threadpool calls are superfluous, calling directly to the async methods would be the correct thing, but that had to not influence on memory leakage inside a webclient. As i said WebClient inherently leaks meory (at least in the fw 2.0, since then I only used HttWebRequests because

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
workqueue is not webclient. RTFM On Sat, Nov 26, 2011 at 11:44 PM, Agustin Gimenez wrote: > Are YOU so moron that you don't see what that program does?? > > Creates a thread, the thread starts an async call, when the call is finished > a new thread is created and the process starts again. A worker

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Agustin Gimenez
Are YOU so moron that you don't see what that program does?? Creates a thread, the thread starts an async call, when the call is finished a new thread is created and the process starts again. A workerthread is automatically disposed when its main function is finished, so there is going to be only

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
maybe you guys should read up on garbage collection, references, and scope and see why his code is crap. queueworkeritem does not have anything to do with async calls. STop freekin using it. I mean, it's like asking why your cake is burned when you keep setting the oven to 500. If you can't see

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
further more, Like it said. It's scope. It's like he has an infinitely recursive program. It doesn't take a genius to see that. ARe you all bad programmers? ___ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximi

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
gusman, way to repeat everything i just said. On Sat, Nov 26, 2011 at 10:43 PM, Gusman wrote: > Sayed, you are helping no one. > > John is triying to know if the webclient leaks memory, so he wrote a cyclic > app which calls DownloadString recursively to test those leakages. > > John, my experien

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Gusman
Sayed, you are helping no one. John is triying to know if the webclient leaks memory, so he wrote a cyclic app which calls DownloadString recursively to test those leakages. John, my experience, at least on Windows is that the webclient leaks memory with async calls. Using workerthreads is only a

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
sorry if my responses seem harsh but you didn't even read my solution before replying back. REad all my emails. If you reply back with anything short of a thank you then i'm not helping you anymore. On Sat, Nov 26, 2011 at 10:03 PM, Sayed Arian Kooshesh wrote > but let me make it SUPER clear sinc

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
what you don't freekin understand cuz you are a crap coder, is scope. Don't call your function recursively, even if it's just getting queued. Unless you want that behavior. GOD On Sat, Nov 26, 2011 at 9:24 PM, SRI wrote: > Hi Sayed, > >        It is not Crap Code. It is a minimum code for testin

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
sorry if that seems a little harsh bit it seems you just want a solution or someone to fix it for you. I gave you the hints and answers you need. If you can't fix it, then you aren't a programmer. It is so obvious what's wrong. while not just write this while(true) { } that's your hint why you

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
but let me make it SUPER clear since you are not reading my emails. REMOVE THE QUEUEWORKERITEM the problem is with your code, not webclient On Sat, Nov 26, 2011 at 10:03 PM, Sayed Arian Kooshesh wrote: > hello. > > it is crap code. I gave you solution. You are not proficient enough to > use it

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
hello. it is crap code. I gave you solution. You are not proficient enough to use it. Hire a real programmer. On Sat, Nov 26, 2011 at 9:24 PM, SRI wrote: > Hi Sayed, > >        It is not Crap Code. It is a minimum code for testing about > Memory Leak Observed in Web Client which he is sharing wi

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread SRI
Hi Sayed, It is not Crap Code. It is a minimum code for testing about Memory Leak Observed in Web Client which he is sharing with the Community. It is something which will help a lot of people if a solution is found. (At least it will warn people of the dangers of usage of Web Cli

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
I'm replying to the thread, not you specifically. Jack's code is some piece of crap it looks like a student programmer wrote. On Sat, Nov 26, 2011 at 9:13 PM, SRI wrote: > Hi Sayed, > >        I never wrote the Code, which you seem to think i did. > >        Did you at least download the project

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread SRI
Hi Sayed, I never wrote the Code, which you seem to think i did. Did you at least download the project which Jack attached?, which he wrote and I did not write. Background Worker is for implementing Async Methods, WebClient / WebRequest is for doing Web Requests

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
some more thoughts. webclient is not part of a threadworkerqueue. Why are you calling anything with threadworkerqueue? ... iw onder if that's your problem. oh no are you requeuing the same function over and over again? take out that damn reference to threadworkerqueue and see your program work

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
also, webclient is a wrapper of this: http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.aspx and backgroundworker. so. Stop using it. Use the smaller pieces. That's my advice. However, I know the problems you are gonna face. This is just the tip. So i really suggest you hire a p

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
Hi! I read your thread. Looked at your code. If you don't know how to use background worker then you really shouldn't be programming in this language as it's a core piece. Either hire a pro, or use java.. On Sat, Nov 26, 2011 at 9:00 PM, SRI wrote: > Hi, > >         Before responding, can you

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread SRI
Hi, Before responding, can you please take the time to read the full thread. My Response was to Jack's issue about a Massive Memory Leak observed in his enclosed project. (Did you see the Project?) I just pointed out by googling that WebClient has issues with Memory an

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Sayed Arian Kooshesh
Use backgroundworker, not an async. Silly. you're using very outdated code. What did google threading? Googling code is like sticking your wang in a glory hole. You're not gonna get anything good.And you may come out with more problems than you went in with. So also, webclient i think wraps back

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread SRI
Hi Jack, Please read this Issue http://forums.silverlight.net/t/12237.aspx/1 on your Memory Leak and other issues with WebClient. May be you have to call WebClient.CancelAsync() as discussed in the above article. I am not an Expert on MonoDroid, but when I looked at your co

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Jack Bond
Thanks for confirming Axel. In the primary application which exposed this issue, I've put in a button to force a garbage collection, and that typically triggers a crash. I've never seen the memory usage drop by 16MB though. I'm building an application that needs to consistently run at least 12 hour

Re: [mono-android] Simple project with massive memory leak

2011-11-21 Thread Axel Busch
Jack, the application leaks memory on my setup as well (Mono 2.10.6, MonoDevelop 2.8.2, MfA 1.2.26517.92876504, Galaxy S II (2.3.3)). _CurrentProcess.PrivateMemorySize64 keeps rising until it hits ca. 52MB, then it drops down to ca. 36MB and starts rising again. Eventually the application exi

[mono-android] Simple project with massive memory leak

2011-11-21 Thread Jack Bond
Hi Everyone, The project I've attached has a single activity that does a single web service call, but it leaks memory massively on my wifi galaxy tablet and galaxy S II phone. They are both up to date with the latest software. Can someone be kind enough to compile/run this project and confirm that