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
Developer Community or GitHub 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.
Like I already wrote: I start my app several houndred times a day. Two times it crashes. If I was to reproduce this with a simple test app, I'd sit there for ages. I would just like you to make sure that there hasn't been a small change that could cause the issue.
Yes, I know, and the very first thing I did was review the 2 pages of diffs between 4.2.1 and 4.2.2 and there was absolutely nothing that changed in the networking stack or anything that the networking stack depends on.
The only changes were to crypto, UIKit, AVFoundation, and the pdf API.
Jeff, crypto might be involved here. René will have to confirm whether he is using "https" or just "http".
There's a single 'mono' revision change between monotouch 4.2.1 and 4.2.2 and it's not related to crypto.
Sebastien, the single change to Mono is a Makefile change that defines FULL_AOT_RUNTIME which X509ExtensionCollection.cs does use...
However, looking at the code, it looks like the purpose of the #if FULL_AOT_RUNTIME block is to avoid reflection (assuming I read that correctly?)
We could build a monotouch.dll with that #define disabled and see if that fixes it for Rene if he is using https .
Oh, I also missed that this #define does change a fair bit of System.Linq code paths.
well, I should say, disables a lot of Linq.
Right, that X509ExtensionCollection.cs avoid reflection/cryptoconfig and helps the linker.
Other LINQ removal are related to code generation and were the cause for another regression (bug #587) unless the linker was used (because it would remove most of the code that the define avoids).
I don't see how that could interact with to cause the stack trace. René could you confirm:
a) if you're using HTTP or HTTPS ? and
b) if the behavior seems identical depending on your linker settings (e.g. comparing "Don't link", the default on the simulator, with "Link SDK assemblies", the default on the devices).
I am indeed using SSL/HTTPS. I have seen it on the simulator only so far but I think its just that chances are higher because of the many testruns I do on the simulator.
René, as we don't have a test case to duplicate your issue we'll need your help to try with only HTTP (i.e. without SSL) and also test for (b). Thanks.
note: bug #587 only occured on devices when "Don't link" was used so I don't think this is the same issue
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.