[Mono.Android] Abort in-flight body I/O on response dispose

src/Mono.Android/Xamarin.Android.Net/AndroidHttpResponseMessage.cs

@@ -1,6 +1,8 @@
+using System;
 using System.Collections.Generic;
 using System.Net.Http;
 
+using Android.Runtime;
 using Java.Net;
 
 namespace Xamarin.Android.Net
@@ -39,14 +41,31 @@ public AndroidHttpResponseMessage (URL javaUrl, HttpURLConnection httpConnection
 
 		protected override void Dispose (bool disposing)
 		{
-			base.Dispose(disposing);
+			// Dispose the content first (base.Dispose). For a streaming response the content is a
+			// CancellationAwareResponseStream, which safely aborts any in-flight read and closes the
+			// underlying stream + connection itself (see AndroidMessageHandler.CancellationAwareResponseStream).
+			base.Dispose (disposing);
 
 			if (javaUrl != null) {
 				javaUrl.Dispose ();
 			}
 
 			if (httpConnection != null) {
-				httpConnection.Dispose ();
+				// Release the connection with Disconnect(), never Dispose(), on the Java peer:
+				//  * Disconnect() closes the socket and aborts any in-flight read. It is the backstop for
+				//    non-streaming responses (e.g. the buffered StringContent error paths) whose content does
+				//    not own the connection; for a streaming response the content already disconnected via
+				//    base.Dispose above, and Disconnect() is idempotent.
+				//  * Disposing the peer (deleting its JNI global reference) could race a body read still
+				//    unwinding on another thread and crash; the peer is reclaimed on finalization.
+				// This runs synchronously on the disposing thread (which may be the UI thread, e.g. gRPC
+				// cancelling from a UI callback): closing a socket is fast and, unlike connect/read/write,
+				// does not trigger NetworkOnMainThreadException.
+				try {
+					httpConnection.Disconnect ();
+				} catch (Exception ex) {
+					Logger.Log (LogLevel.Info, AndroidMessageHandler.LOG_APP, $"Disconnection exception: {ex}");
+				}
 			}
 		}
 	}