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.
mono_jit_cleanup () is the proper way to shut down the runtime. As a workaroud, you can avoid calling it.
Can you provide a test case that shows the crash on regular mono?
The attached test crashes on regular mono.
Dmitriy, looks like you forgot to attach the file.
Created attachment 7643 [details]
Created attachment 7644 [details]
Attached simple (Linux C++) test.cpp and test.cs which calls HttpWebRequest.GetResponseStream(), and crashes upon mono_jit_cleanup(), which is assuredly related to the original bug report.
Skipping mono_jit_cleanup() per Zoltan's suggestion does work around the issue.
Crashes seem to segfault or fail assertion with mono_mutex_lock. Seems to be related to threading since errors opening '/proc/...' are output after the calling executable has exited.
Works fine running without embedding the Mono runtime. Happens on the latest Mono also.
Debug info from gdb:
Bad call to mono_mutex_lock result 22
* Assertion at marshal.c:2377, condition `ret == 0' not met
(( linux-shell-prompt )) warning: unable to open /proc file '/proc/25287/status'
warning: unable to open /proc file '/proc/25287/status'
ptrace: No such process.
Can't reproduce this using the testcase. What mono version is this ?
If you can you still reproduce with latest mono version, please feel free to reopen this bug. Thank you.