[Mono-bugs] [Bug 541194] New: mono_image_close causes sigsegv on some multi-core systems
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Tue Sep 22 16:12:28 EDT 2009
http://bugzilla.novell.com/show_bug.cgi?id=541194
Summary: mono_image_close causes sigsegv on some multi-core
systems
Classification: Mono
Product: Mono: Runtime
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: misc
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: christian.hergert at gmail.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
There seems to be a race condition in mono_image_close(). Leaking memory and
returning right away seems to prevent mono from crashing.
Below is a stack trace of the issue exemplified by MonoDevelop which uses
Assembly.GetAssemblyName() pretty heavily now.
Attached is a gdb backtrace of all threads.
Reproducible: Sometimes
Steps to Reproduce:
1. Start a program that does lots of assembly opening and let the refcount fall
to 0 on a multi-core box. The more cores the better.
2. Repeat until it happens. Perhaps hellgrind can be of some use.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list