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 for Bug 32128 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I tried to use Mono 4.0 runtime on Windows 8.1. My app contains NancyFx (https://github.com/NancyFx/Nancy), a framework for building REST services. When I run my test app on windows with nancy self-hosting and MS .Net framework, it works really good. But, when executed with mono (on windows also), it lacks performance and gives me a little strange responses.
For example, for a simple method like below:
Get["/IsActive"] = param =>
var json = Response.AsJson(true);
I get simply true in .net execution and
P/1.1 200 OK
Content-Type: application/json; charset=utf-8
Date: Mon, 13 Jul 2015 18:05:24 GMT
and on mono I get this response really slow. I guess it's some mono issues with HttpHandler or something...
To reproduce this bug simply create Nancy self-hosted app with the registration below (you can find examples on Nancy github page) and try to consume it.
Please provide self contained repro for your issue
This was already reported in Bug 30065. That bug has an attached solution that shows the problem.
Also, we see this with both Nancy and WebAPI. Bug 30065 reproduced it by using OWIN middleware without a framework like WebAPI or Nancy.
Is there any update?
I left a comment on BUG 30065 as well and I can post another self-contained reproduction if requested.
Is there any news about this problem? I'm using mono 184.108.40.206 x64 and there the problem still exists