|
Hi, The background
to our problem is that we are deploying a large website on mono for a customer,
and have the server 'freeze' about 1-2 times a day. At the freeze points mono
takes up between 15-55% of memory on the web server, typically consumes around
3% of CPU, and the website becomes responsive again if the mono processes are
restarted. The freeze is
completely random. When we run strace we get copius output into the trace logs
resulting in a large build-up in the log size. We are therefore forced to stop
the trace because of this. Gdb kills the running application, so we don’t
use it. Is there another
way of running the trace for days on-end without producing voluminous (and
perhaps unnecessary) data? Regards Garikai
Tachiwona |
- [Mono-list] Mono Issue Garikai Tachiwona (DSL AK)
- Re: [Mono-list] Mono Issue Miguel de Icaza
- RE: [Mono-list] Mono Issue Garikai Tachiwona (DSL AK)
- RE: [Mono-list] Mono Issue Miguel de Icaza
- RE: [Mono-list] Mono Issue Miguel de Icaza
- RE: [Mono-list] Mono Issue Dilton McGowan II
- RE: [Mono-list] Mono Issue Miguel de Icaza
- Re: [Mono-list] Mono Issue James Grant
- RE: [Mono-list] Mono Issue Garikai Tachiwona (DSL AK)
- RE: [Mono-list] Mono Issue Garikai Tachiwona (DSL AK)
- RE: [Mono-list] Mono Issue Gonzalo Paniagua Javier
