[Mono-list] Announcing the release of Mono 2.4.3: bugs found

Maxim makska at yandex.ru
Fri Dec 11 18:24:00 EST 2009


Unfortunately it happen again.
So, I've filed this bug: https://bugzilla.novell.com/show_bug.cgi?id=564236
I'll  downgrade Mono to 2.4.2.2 today night.

All the best,
Max Karavaev

Maxim wrote:
> Hi Robert,
>
> I've updated Mono from 2.4.2.2.
> Issue like described occurs in previous version too, but in other manner
> and not so often. It happens several times per week with records in
> apache error log like:
> Stack overflow in unmanaged: IP: 0x573940, fault addr: 0x496cddd8
> Stacktrace:
>
> Native stacktrace:
>     /opt/mono/bin/mono [0x47e7a0]
>     /opt/mono/bin/mono [0x4ada8d]
>     /lib64/libpthread.so.0 [0x3e3e60e4c0]
>     /opt/mono/bin/mono [0x47efbe]
>     /opt/mono/bin/mono [0x47bf76]
>     [0x411c5278]
>
> Debug info from gdb:
>
> [Tue Dec 08 19:21:23 2009] [notice] child pid 4911 exit signal
> Segmentation fault (11)
> [Tue Dec 08 19:21:23 2009] [notice] child pid 5566 exit signal
> Segmentation fault (11)
> ....
> After it nagios reported for all web-sites in this shared pool: HTTP
> CRITICAL - No data received from host.
> Other websites (more loaded) in isolated pools works just fine on both
> Mono versions.
>
> But also I have a goods news!  It seems like I've found workaround for
> this issue. I've added line
> MonoSetEnv MONO_THREADS_PER_CPU=2000
> to mod_mono.conf. And today all works just fine whole day long.
> Of course we need to test it for about one week to say "YES!" :)
>
> I think it would be great to rewrite page
> http://www.mono-project.com/Mod_mono and describe such a situations more
> detailed.
>
> Thanks!
>
> With best wishes,
> Max Karavaev
>
>
> Robert Jordan wrote:
>   
>> On 10.12.2009 21:10, Maxim wrote:
>>   
>>     
>>> 2) stability. For about two times per day main instance of
>>> mod-mono-server unexpectedly jumps from  2Gb of memory consumption up to
>>> 15-20Gb, and eat all server resouses, for example:  # top
>>>     
>>>       
>> There were no changes in 2.4.3 that could cause this regression.
>>  From which version did you update to see that?
>>
>> Robert
>>
>> _______________________________________________
>> Mono-list maillist  -  Mono-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-list
>>
>>   
>>     
>
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>
>   



More information about the Mono-list mailing list