[Mono-dev] Mono 126.96.36.199 review (bugs and conclusion)
Miguel de Icaza
miguel at ximian.com
Sun Mar 23 23:12:51 EDT 2008
Thanks for the post.
> 1. We have more and more problems related to
> https://bugzilla.novell.com/show_bug.cgi?id=322400 (SOAP Client code)
Can you isolate this bug and reproduce without the server using it?
This sound like you could be running out of threads in the thread pool,
Could you increase the number of threads in the thread pool and let us
know if that fixes the problem?
> 2. Handles leak problems :
> This is a recurrent problems with mono.
> I ever talk about my problem on :
> http://lists.ximian.com/pipermail/mono-devel-list/2008-February/026981.html and on http://lists.ximian.com/pipermail/mono-devel-list/2008-February/027015.html
> Today i've a workaround (bad)
> -> I've isolated MONO_SHARED_DIR for each ASP.NET application (now
> i've 4096 handles by apps)
> -> a zabbix server (monitoring) send a request on an aspx web page
> that does a GC.Collect(); for each ASP.NET application-> this works
> well handles doesn't leak anymore
We are working on this particular problem.
Since we have not had any luck reproducing these problems, we are
working on a more general solution. If we could reproduce this
problem, we would be able to come up with a simpler solution though.
The only way of finding where this problem is happening is by
identifying where those handles are being leaked, getting a list of the
handle types would be a useful first step:
> https://bugzilla.novell.com/show_bug.cgi?id=342190 (with sharpZipLib)
Yeah, this is something that would be useful to profile; Marek had
some hints in the post as to things that could be improved, but as far
as I know, nobody has tried to address this.
> https://bugzilla.novell.com/show_bug.cgi?id=357947 (System.Data)
It seems like Varadhan has been looking at this. Varadhan?
More information about the Mono-devel-list