[Mono-list] mono app receives SIGSEGV after running for 20 hours!!

S Umadevi sUmadevi@novell.com
Tue, 10 May 2005 23:21:18 -0600

Hi Gonzalo
 Had a look at the code, There was a while true loop where the listener
callback object was getting created and the socket usage in the callback
was not correct. Once these are corrected, I guess we will not see the
issue anymore..



>>> gonzalo@ximian.com 05/11/05 7:26 AM >>>
On Tue, 2005-05-10 at 18:50 +0530, Kala B wrote:
> Hi,
> I have a C# application running on mono/Suse Linux. Its basically a
> Unix Domain Socket server ( uses Mono.Posix for the socket APIs). 
> code runs perfectly for almost 20 hours. When there is just no
> activity ( the application is just listening and there are no
> connecting to it), the application receives a SIGSEGV. It just
> receives a Segmentation fault.
> My code does not have any P/Invoke calls. 
> Could you please guide me as to how to go about resolving this issue?

> I can think of the following possibilities : 
> 1. Memory leak in my application - but memory is completely managed
> the run-time, so could this be really an issue with my application?

You might still have a leak by keeping references to objects around.

> 2. Some problem with Mono.Posix ( because of some P/Invoke?? ) 

mod-mono-server (xsp module in svn) does exactly that. I've never
running it for 24 hours with no clients, but with clients, it works

> 3. Peridically I have a thread which wakes up, checks something and
> sleeps again. It uses a mutex. Could that be some issue?

No. mod-mono-server does much more than that and no problems at all.

> How do I detect if it is a mono run-time/mono package issue or an
> issue with my code?
> The mono version I use is 1.0.4, but the same problem was detected
> mono 1.1.4 too.
> Could you please guide me?

I'd recommend using 1.1.7 instead.


Mono-list maillist  -  Mono-list@lists.ximian.com