[Mono-bugs] [Bug 384024] New: Native code crashes when using Avahi provider under Banshee - threading issues ?

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=384024


           Summary: Native code crashes when using Avahi provider under
                    Banshee - threading issues?
           Product: Mono: Class Libraries
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Mono.Zeroconf
        AssignedTo: abockover at novell.com
        ReportedBy: hixon.alexander at mediati.org
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


When using Mono.Zeroconf under Linux and the Avahi provider, said application
will occasionally crash either during start up; while attempting to resolve a
newly exposed service on the network, or; will fail to resolve a service even
though it is visible to all other applications. Further investigates suggest
that MZ can see the share, but not actually resolve to the address provided.

For the most part, the code to search for a service looks something like this:
locator = new ServiceLocator ();
locator.Found += OnServiceFound;
locator.Removed += OnServiceRemoved;
locator.ShowLocalServices = true;
locator.Start ();

Which in turn creates an instance of a ServiceLocator object. Note that here,
we don't use any threading (although we do when connecting to a share, but we
crash before that anyway).

Two things generally happen when we run this code: a) Banshee will crash
ungracefully due to unmanaged code issues, or b) no services will be resolved.

For the most part, the thread managing the service location will crash, but the
stacktrace will almost always be useless, because it will appear the crash
happened elsewhere.

Full backtrace from threads via GDB might be useful here? Will have to
investigate some more if I have time.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.