Bug 34491 - Crash in Http stack #2
Summary: Crash in Http stack #2
Alias: None
Product: iOS
Classification: Xamarin
Component: BCL Class Libraries ()
Version: XI 8.9.x (iOS 8.3)
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-10-01 12:46 UTC by Grigory (Playtika)
Modified: 2017-07-25 13:41 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Grigory (Playtika) 2015-10-01 12:46:49 UTC
System.NullReferenceException: Object reference not set to an instance of an object
  at System.Net.WebConnection.ReadDone (IAsyncResult result) [0x00000] in <filename unknown>:0  (code.cs:1)
Comment 1 Rodrigo Kumpera 2015-10-01 13:40:51 UTC
Please provide a test case that demonstrates the issue so we can fix it.
Comment 2 Grigory (Playtika) 2015-10-01 13:53:18 UTC
NullRef, what repro do u need...
Comment 3 Rodrigo Kumpera 2015-10-01 14:56:06 UTC
Without further information, like a test case, there's no way for us to tell whether a given change will fix your issue or not.
Comment 4 John Miller [MSFT] 2017-07-25 13:41:46 UTC
Because we have not received a reply to our request for more information, we are marking this issue as RESOLVED→NORESPONSE. If you are still encountering this issue on the latest Xamarin.iOS, please don’t hesitate to reopen the ticket with the requested information. Thanks!