Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 10294 [details]
resgen binary and .resx with images
at <unknown> <0xffffffff>
*** Error in `/usr/bin/mono': malloc(): memory corruption: 0x0000000001fcf5c0 ***
here is more details:
some files are attached to this bug.
zip archive contains run.sh file with the command to reproduce bug
several stack traces (mono --trace)
output of valgring:
(it shows access violation of sgen code)
one more valgring now with names - https://gist.github.com/anonymous/ed52b86c4ee13f811d8b
What mono version is this and what os/architecture ?
you can see this in logs.
mono is from master (but Mono, Version 126.96.36.199 doesn't work also)
architecture is x86_64
Mono JIT compiler version 4.1.0 (branch-master/6397c8d Mon Mar 9 20:48:09 MSK 2015)
also crashes on mono 3.12.0
# mono -V
Mono JIT compiler version 3.12.0 ((detached/a813491 Fri Mar 13 09:53:49 MSK 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
LLVM: supported, not enabled.
Hello Arsen. Are you still able to get this behavior ? I have run 3 instances of run.sh in parallel for over 12 hours but wasn't able to get a crash ? I tried an older 4.0 since that was supposed to fail, on an 16.04 amd64 ubuntu. Nor was I able to repro with latest mono.
Could you provide a stacktrace of the crash if you are able to get it ? (run with MONO_DEBUG=suspend-on-sigsegv, then attach once it crashed with gdb and run "thread apply all bt")
I can't reproduce it now, because i recompiled mono runtime. I believe that problem not solved, but can't provide more info now.