[Mono-dev] xbuild crash with mono 4.6.1?
vlbrez at microsoft.com
Thu Oct 20 00:19:33 UTC 2016
Would it be possible to repro this issue ? Is this project available somewhere ?
If it’s not an OOM issue, then additional debugging would be required. Judging from the stacktrace and source code, mono_valloc/mono_valloc_aligned fails for whatever reason. Either desc is corrupted (it would be useful to know the contents of the memory there) and we are trying to allocate invalid amounts of memory, or the mmap behind the scenes fails for other reasons (in which case it would be useful to know the errno value). This information should not be too hard to find by attaching with lldb/gdb (MONO_DEBUG=suspend-on-sigsegv can be passed if the debugger does not attach automatically).
Ideally it would be nice to see this crash myself, but I’m not sure whether this is possible.
From: David Evans <devans at pacificbiosciences.com>
Date: Thursday, 20 October 2016 at 02:20
To: Vlad Brezae <vlbrez at microsoft.com>, mono-devel <mono-devel-list at lists.ximian.com>
Subject: RE: [Mono-dev] xbuild crash with mono 4.6.1?
Thanks, Vlad. I did check that first and though xbuild uses an insane amount of memory there still was tons left when it crashed. I did some profiling yesterday to confirm and it’s crashing when there are still gigs of physical memory available plus all of the swap. Which is why I suspected some kind of heap corruption as a more likely cause.
I just noticed that I was testing against the 18.104.22.168 source package, I can try 22.214.171.124 as well. I can also try earlier builds of 4.x to see where it might have been introduced, but that will take me some time. Sounds like this is not a known issue to folks here?
I did just find two open Bugzilla reports that looks similar but not exactly the same, against 4.6.0, but without any resolution or diagnosis yet. I just added notes to these:
And also this building in XS reported for 4.6.0:
From: Vlad Brezae [mailto:vlbrez at microsoft.com]
Sent: Tuesday, October 18, 2016 2:11 PM
To: David Evans <devans at pacificbiosciences.com>; mono-devel <mono-devel-list at lists.ximian.com>
Subject: Re: [Mono-dev] xbuild crash with mono 4.6.1?
Based on the crash site, it would seem that we fail to allocate memory from the OS, which means we have an OOM situation, which we poorly handle as of right now.
Could you check whether this is the case, whether there are mono instances that use more memory than expected. You could consider trying to limit the heap from growing too much by passing MONO_GC_PARAMS=soft-heap-limit=<heap_limit>, unless something is leaking.
From: Mono-devel-list <mono-devel-list-bounces at lists.dot.net<mailto:mono-devel-list-bounces at lists.dot.net>> on behalf of David Evans <devans at pacificbiosciences.com<mailto:devans at pacificbiosciences.com>>
Date: Tuesday, 18 October 2016 at 20:50
To: mono-devel <mono-devel-list at lists.ximian.com<mailto:mono-devel-list at lists.ximian.com>>
Subject: [Mono-dev] xbuild crash with mono 4.6.1?
I just started building and testing with mono 4.6.1 and I’m seeing an intermittent crash (memory corruption?) now during the build. Happens for me about one time out of ten. Anyone else seeing this or is there a solution already available that I could patch with? We have a fairly large project which uses a lot of memory, but I haven’t seen anything like this building with 126.96.36.199 or when I tried out 4.2.x or 4.3.x Thanks!
Appears to be crashing in sgen when allocating, hence my corruption guess.
Full traces here:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list