Bug 39019 - Crash in networking layer
Summary: Crash in networking layer
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: Mono runtime / AOT compiler ()
Version: XI 9.4 (iOS 9.2)
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Ludovic Henry
URL:
Depends on:
Blocks:
 
Reported: 2016-02-22 21:13 UTC by Grigory (Playtika)
Modified: 2017-03-14 01:09 UTC (History)
7 users (show)

Tags:
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:
Status:
RESOLVED NORESPONSE

Description Grigory (Playtika) 2016-02-22 21:13:49 UTC
ONLY reproduces on iPhone 6, 6S, 6Plus, 6S Plus, iPad AIR2, iPad PRO, iPad mini 4. 
All of them are arm64 with A8/A9 cpu.

I have no repro case/steps/project whatever. We only have 150 crashes on 1.5million DAU. Definitely not easy to reproduce, but CPU/AOT related bugz are something very scary.


System.ArgumentException: Either the IAsyncResult object did not come from the corresponding async method on this type, or the End method was called multiple times with the same IAsyncResult.
Parameter name: asyncResult
  at System.Threading.Tasks.TaskFactory`1+FromAsyncTrimPromise`1[TResult,TInstance].CompleteFromAsyncResult (IAsyncResult asyncResult) <0x1013aa054 + 0x00158> in <filename unknown>:0  (code.cs:1)
  at System.Net.SimpleAsyncResult+<SimpleAsyncResult>c__AnonStorey0.<>m__0 (System.Net.SimpleAsyncResult result) <0x1015fd41c + 0x00023> in <filename unknown>:0  (code.cs:1)
  at System.Net.WebConnectionStream.ReadCallbackWrapper (IAsyncResult r) <0x1016024e8 + 0x000af> in <filename unknown>:0  (code.cs:1)
  at System.Net.Sockets.SocketAsyncResult.<ExecuteWorkItem>m__1 (System.Object state) <0x1015df1ec + 0x00053> in <filename unknown>:0  (code.cs:1)
  at (wrapper managed-to-native) System.Runtime.Remoting.Messaging.AsyncResult:Invoke (System.Runtime.Remoting.Messaging.AsyncResult) (code.cs:1)
  at System.Runtime.Remoting.Messaging.AsyncResult.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () <0x10136b238 + 0x0000b> in <filename unknown>:0  (code.cs:1)
  at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x10141b140 + 0x001df> in <filename unknown>:0  (code.cs:1)
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x101326acc + 0x0000b> in <filename unknown>:0  (code.cs:1)
Comment 1 Lars Ryssel 2016-05-26 18:02:05 UTC
We are having the same problem, and we can't reproduce it, it only happens rarely, but it kills our app.
Comment 2 Fabien Molinet 2016-05-30 09:13:11 UTC
Same bug here. It is really annoying since it is quite random.
Comment 3 David Laundav 2016-06-15 19:17:22 UTC
Same issue here. Our application has crashed around 1200 times the past 30 days and it's really a big pain for our customers. Can this be prioritised, please?
Comment 4 David Laundav 2016-06-15 19:22:58 UTC
I forgot to mention, that the crash for us happens on Android, and not on iOS. This happens mostly on older devices (4.2, 4.4, 4.1 and 4.0.4) but has also occurred a few times sometimes on 5.0. We also, cannot reproduce the crash, and thus have no definite reproduction steps/samples to provide.

The stack trace is:

System.ArgumentExceptionEither the IAsyncResult object did not come from the corresponding async method on this type, or the End method was called multiple times with the same IAsyncResult. Parameter name: asyncResult

  at System.Threading.Tasks.TaskFactory`1+FromAsyncTrimPromise`1[TResult,TInstance].CompleteFromAsyncResult (IAsyncResult asyncResult) [0x00069] in <filename unknown>:0 
  at System.Net.Sockets.SocketAsyncResult.<ExecuteWorkItem>m__1 (System.Object state) [0x00000] in <filename unknown>:0 
  at (wrapper managed-to-native) System.Runtime.Remoting.Messaging.AsyncResult:Invoke (System.Runtime.Remoting.Messaging.AsyncResult)
  at System.Runtime.Remoting.Messaging.AsyncResult.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00000] in <filename unknown>:0 
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <filename unknown>:0 
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <filename unknown>:0  

ParamName	asyncResult
HResult         -2147024809
TargetSite	CompleteFromAsyncResult
Comment 5 Rodrigo Kumpera 2017-02-07 21:24:32 UTC
Ludovic,


Can you give us an update on this bug?
Comment 6 Ludovic Henry 2017-02-07 21:29:29 UTC
I could never reproduce this bug, and never witnessed it. If anybody can provide even a semi-reliable repro, then I will be happy to have a look at it.
Comment 7 Timothy Risi 2017-03-14 01:09:12 UTC
We have not received the requested information. If you are still 
experiencing this issue please provide all the requested information 
and re-open the bug report. Thanks!