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.
I wish I could include a test case however this bug only seems to happen very randomly, and writing a test case that does 1000 web requests doesn't seem to trigger it.
I can provide a stacktrace: http://pastebin.com/RAAbaq2g
And the source code where it happens: https://github.com/Goz3rr/GozBot/blob/master/GozBot2/Util.cs#L109
In the stack trace I was retrieving something from the YouTube API however it happens with different sites as well, such as the Twitter API and obviously only when requesting over HTTPS. Immediately after this exception is thrown (after 40 seconds every time, so I assume it's some kind of timeout) requesting the same URL again works just fine. It doesn't seem to happen on windows either. I have tried compiling with Visual Studio 2013 and then uploading the exe or using xbuild on the server and in both builds the bug appears. I'm using 'mono --debug application.exe' to start the application.
Mono JIT compiler version 4.0.1 (tarball Thu May 28 09:08:28 UTC 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
LLVM: supported, not enabled.
Server (OpenVZ VPS):
Debian GNU/Linux 7.8 (wheezy)
Kernel 2.6.32-042stab090.5 x86_64
We'll need any kind of repro for the issue
Yeah I was afraid that would be the issue, as of right now I have no idea how to reproduce it so would there be a way to turn on some additional debugging that could help?
We don't really have any there but any test case even if it takes long time is fine
Please reopen when you have some repro