Will take a look. Not sure what it may not be liking. Code is very basic.
Literally allocates 16mb chunk then frees it (each object has one) code
works fine in windows with same calls. Will debug it on Sunday.
On Friday, August 24, 2012, Jonathan Pryor wrote:
On Aug 23, 2012, at 2:35 AM, Greg
On Aug 23, 2012, at 2:35 AM, Greg Young gregoryyou...@gmail.com wrote:
We are allocating and releasing unmanaged memory with marshal.allochglobal.
In mono we are getting the following failure (no failures under clr).
Any ideas?
That's not a mono error, that's a glibc assert (and thus cannot
This crash is either a bug on glibc malloc, which I find to be the less
likely, or a bug on mono or your app.
Run it under the many malloc debugging tools that malloc(3) has or with a
tool such as valgrind - it will very
easily spot a memory overrun in mono/your app.
On Fri, Aug 24, 2012 at
We are allocating and releasing unmanaged memory with marshal.allochglobal.
In mono we are getting the following failure (no failures under clr).
Any ideas?
part from team city logs:
[20:55:52][Step 2/2] mono: malloc.c:2451: sYSMALLOc: Assertion `(old_top ==
(((mbinptr) (((char *)
Either your app is broken or linux's malloc is. Mono does nothing special
but call malloc/free.
One issue might be if you're allocating more than 2Gb of memory at once.
This will probably break on mono.
On Thu, Aug 23, 2012 at 3:35 AM, Greg Young gregoryyou...@gmail.com wrote:
We are
Didn't reply to all.
Code is very simple (allocates 16 mb and frees it).
Also this in an internal assertion is this really the best way? If we
passed wrong parameters etc I would kind of expect an exception.
On Friday, August 24, 2012, Rodrigo Kumpera wrote:
Either your app is broken or
