[Mono-bugs] [Bug 675055] New: Assertion at sgen-gc.c:2192, condition `mem' not met

[bugzilla_noreply at novell.com]

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

https://bugzilla.novell.com/show_bug.cgi?id=675055#c0


           Summary: Assertion at sgen-gc.c:2192, condition `mem' not met
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.10.x
          Platform: x86-64
        OS/Version: SLES 11
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GC
        AssignedTo: lupus at novell.com
        ReportedBy: maciej.paszta at mlabs.pl
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.82 Safari/534.16

After a couple of hours application crached with the following native stack
trace:

* Assertion at sgen-gc.c:2192, condition `mem' not met

Native stacktrace:

        /usr/bin/mono-sgen() [0x497578]
        /lib64/libpthread.so.0(+0xf5d0) [0x7fcefced35d0]
        /lib64/libc.so.6(gsignal+0x35) [0x7fcefcb98945]
        /lib64/libc.so.6(abort+0x181) [0x7fcefcb99f21]
        /usr/bin/mono-sgen() [0x6019ef]
        /usr/bin/mono-sgen() [0x601a87]
        /usr/bin/mono-sgen() [0x5101b3]
        /usr/bin/mono-sgen() [0x53326c]
        /usr/bin/mono-sgen() [0x533363]
        /usr/bin/mono-sgen() [0x53346d]
        /usr/bin/mono-sgen() [0x5337a2]
        /usr/bin/mono-sgen() [0x506889]
        /usr/bin/mono-sgen() [0x512802]
        /usr/bin/mono-sgen() [0x513d9a]
        /usr/bin/mono-sgen() [0x5142ca]
        /usr/bin/mono-sgen() [0x51473e]
        [0x415accdd]

Just after the application craches memory consuption sky rockets (from 300MB to
around 2GB). This doesn't happen when using BoehmGC. Mono is run with
wbarrier=remset,collector=marksweep-par.


Reproducible: Sometimes

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