[Mono-bugs] [Bug 590436] New: mmap failure in System.GC.Internal.Collect() on Xen - x86-64

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue Mar 23 06:24:40 EDT 2010


http://bugzilla.novell.com/show_bug.cgi?id=590436

http://bugzilla.novell.com/show_bug.cgi?id=590436#c0


           Summary: mmap failure in System.GC.Internal.Collect() on Xen -
                    x86-64
    Classification: Mono
           Product: Mono: Runtime
           Version: SVN
          Platform: x86-64
        OS/Version: OES - Linux
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: GC
        AssignedTo: lupus at novell.com
        ReportedBy: peter.cahill at ucd.ie
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB;
rv:1.9.2) Gecko/20100115 Firefox/3.6

I have a program that is using large amounts of RAM (2-3GB). To avoid out of
memory errors at particular times I invoke the GC (GC.Collect()) in my own code
as at these times ~1GB of RAM can be released.

My code works 100% fine on Mono 2.6.3 on Mac OS X, and on Mono 2.6.3 on x86
Linux (debian-based). On 64bit Linux (kernel 2.6.24-26-xen) this produces
SIGABRT, with the error:

mmap(...PROT_NONE...) failed
Stacktrace:

  at (wrapper managed-to-native) System.GC.InternalCollect (int) <0x0004f>
  at (wrapper managed-to-native) System.GC.InternalCollect (int) <0xffffffff>
  at System.GC.Collect () <0x00013>

I have tried both Mono 2.6.3, SVN 142439 and the current (within 24hours)
version from SVN. This issue exists with all. I'm using the default GC:

Mono JIT compiler version 142439 (tarball Mon Mar 22 23:10:34 UTC 2010)
Copyright (C) 2002-2008 Novell, Inc and Contributors. www.mono-project.com
        TLS:           __thread
        GC:            Included Boehm (with typed GC and Parallel Mark)
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  amd64
        Disabled:      none



Reproducible: Always

Steps to Reproduce:
1. Use Mono current version on 64bit-linux, on Xen VM.
2. Call GC.Collect() from code.
3.
Actual Results:  
Software crashes - from SIGABRT being recieved. All data lost.


If you have problems reproducing the bug I can try to make a 'mini' program
that will cause the same bug. Just let me know if you need it.

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


More information about the mono-bugs mailing list