.Net 6 API in failing at start up post this upgrade to VS2022 17.8. Getting error "Operation is not supported on this platform."

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:Multiple people on my team are impacted (internal MSFT only)] [regression] [worked-in:17.7.7]
After upgrading to Visual Studio 2022 18.3, .Net 6.0 API stopped working and failing at startup with error 'Operation is not supported on this platform.'
Stack Trace:
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.AllowedAsciiCodePoints.get_AsVector()
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.GetIndexOfFirstCharToEncodeSsse3(Char* pData, UIntPtr lengthInChars)
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.GetIndexOfFirstCharToEncode(ReadOnlySpan1 data) at System.Text.Encodings.Web.DefaultJavaScriptEncoder.FindFirstCharacterToEncode(Char* text, Int32 textLength) at System.Text.Json.JsonWriterHelper.NeedsEscaping(ReadOnlySpan1 value, JavaScriptEncoder encoder)
at System.Text.Json.Utf8JsonWriter.WritePropertyName(ReadOnlySpan1 propertyName) at System.Text.Json.Utf8JsonWriter.WritePropertyName(String propertyName) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerOptions.Serialize(Utf8JsonWriter writer) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.KestrelEventSource.Configuration(KestrelServerOptions options) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.KestrelEventSource.AddServerOptions(KestrelServerOptions options) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.<StartAsync>d__301.MoveNext()
at Microsoft.AspNetCore.Hosting.GenericWebHostService.d__37.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.<b__15_1>d.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.d__18`1.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.g__LogAndRethrow|15_3(<>c__DisplayClass15_0& )
at Microsoft.Extensions.Hosting.Internal.Host.d__15.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
at BDO.Integration.API.Program.Main(String[] args) in C:\BDO\API\APT_API\BDO.APT.API\src\External.API\WebAPI\Program.cs:line 23

---

Original Comments

(no comments)

---

Original Solutions

(no solutions)

Tagging subscribers to this area: @dotnet/area-extensions-hosting
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This issue has been moved from a ticket on Developer Community.

---

[severity:Multiple people on my team are impacted (internal MSFT only)] [regression] [worked-in:17.7.7]
After upgrading to Visual Studio 2022 18.3, .Net 6.0 API stopped working and failing at startup with error 'Operation is not supported on this platform.'
Stack Trace:
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.AllowedAsciiCodePoints.get_AsVector()
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.GetIndexOfFirstCharToEncodeSsse3(Char* pData, UIntPtr lengthInChars)
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.GetIndexOfFirstCharToEncode(ReadOnlySpan1 data) at System.Text.Encodings.Web.DefaultJavaScriptEncoder.FindFirstCharacterToEncode(Char* text, Int32 textLength) at System.Text.Json.JsonWriterHelper.NeedsEscaping(ReadOnlySpan1 value, JavaScriptEncoder encoder)
at System.Text.Json.Utf8JsonWriter.WritePropertyName(ReadOnlySpan1 propertyName) at System.Text.Json.Utf8JsonWriter.WritePropertyName(String propertyName) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerOptions.Serialize(Utf8JsonWriter writer) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.KestrelEventSource.Configuration(KestrelServerOptions options) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.KestrelEventSource.AddServerOptions(KestrelServerOptions options) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.<StartAsync>d__301.MoveNext()
at Microsoft.AspNetCore.Hosting.GenericWebHostService.d__37.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.<b__15_1>d.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.d__18`1.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.g__LogAndRethrow|15_3(<>c__DisplayClass15_0& )
at Microsoft.Extensions.Hosting.Internal.Host.d__15.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
at BDO.Integration.API.Program.Main(String[] args) in C:\BDO\API\APT_API\BDO.APT.API\src\External.API\WebAPI\Program.cs:line 23

---

Original Comments

(no comments)

---

Original Solutions

(no solutions)

Author:	vsfeedback
Assignees:	-
Labels:	area-Extensions-Hosting
Milestone:	-

Tagging subscribers to this area: @dotnet/area-system-text-encodings-web
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This issue has been moved from a ticket on Developer Community.

---

[severity:Multiple people on my team are impacted (internal MSFT only)] [regression] [worked-in:17.7.7]
After upgrading to Visual Studio 2022 18.3, .Net 6.0 API stopped working and failing at startup with error 'Operation is not supported on this platform.'
Stack Trace:
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.AllowedAsciiCodePoints.get_AsVector()
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.GetIndexOfFirstCharToEncodeSsse3(Char* pData, UIntPtr lengthInChars)
at System.Text.Encodings.Web.OptimizedInboxTextEncoder.GetIndexOfFirstCharToEncode(ReadOnlySpan1 data) at System.Text.Encodings.Web.DefaultJavaScriptEncoder.FindFirstCharacterToEncode(Char* text, Int32 textLength) at System.Text.Json.JsonWriterHelper.NeedsEscaping(ReadOnlySpan1 value, JavaScriptEncoder encoder)
at System.Text.Json.Utf8JsonWriter.WritePropertyName(ReadOnlySpan1 propertyName) at System.Text.Json.Utf8JsonWriter.WritePropertyName(String propertyName) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerOptions.Serialize(Utf8JsonWriter writer) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.KestrelEventSource.Configuration(KestrelServerOptions options) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.KestrelEventSource.AddServerOptions(KestrelServerOptions options) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.<StartAsync>d__301.MoveNext()
at Microsoft.AspNetCore.Hosting.GenericWebHostService.d__37.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.<b__15_1>d.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.d__18`1.MoveNext()
at Microsoft.Extensions.Hosting.Internal.Host.g__LogAndRethrow|15_3(<>c__DisplayClass15_0& )
at Microsoft.Extensions.Hosting.Internal.Host.d__15.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
at BDO.Integration.API.Program.Main(String[] args) in C:\BDO\API\APT_API\BDO.APT.API\src\External.API\WebAPI\Program.cs:line 23

---

Original Comments

(no comments)

---

Original Solutions

(no solutions)

Author:	vsfeedback
Assignees:	-
Labels:	area-System.Text.Encodings.Web, untriaged
Milestone:	-

[ericstj]

I'm a bit puzzled by this callstack.

The GetIndexOfFirstByteToEncodeSsse3 call is under #if NETCOREAPP

runtime/src/libraries/System.Text.Encodings.Web/src/System/Text/Encodings/Web/OptimizedInboxTextEncoder.cs

Lines 350 to 372 in 82d75ad

	#if NETCOREAPP
	if (Ssse3.IsSupported
	#if NET5_0_OR_GREATER
	|| (AdvSimd.Arm64.IsSupported && BitConverter.IsLittleEndian)
	#endif
	)
	{
	int asciiBytesSkipped;
	unsafe
	{
	fixed (byte* pData = data)
	{
	nuint asciiBytesSkippedNInt;
	#if NET5_0_OR_GREATER
	if (AdvSimd.Arm64.IsSupported && BitConverter.IsLittleEndian)
	{
	asciiBytesSkippedNInt = GetIndexOfFirstByteToEncodeAdvSimd64(pData, (uint)dataOriginalLength);
	}
	else
	#endif
	{
	Debug.Assert(Ssse3.IsSupported, "#ifdef was ill-formed.");
	asciiBytesSkippedNInt = GetIndexOfFirstByteToEncodeSsse3(pData, (uint)dataOriginalLength);

But the AsVector throwing path is only for TARGET_BROWSER:

runtime/src/libraries/System.Text.Encodings.Web/src/System/Text/Encodings/Web/OptimizedInboxTextEncoder.Ascii.cs

Lines 25 to 35 in 82d75ad

	#if NETCOREAPP
	#if !TARGET_BROWSER
	[FieldOffset(0)] // ensure same offset with AsBytes field
	internal Vector128<byte> AsVector;
	#else
	// This member shouldn't be accessed from browser-based code paths.
	// All call sites should be trimmed away, which will also trim this member
	// and the type hierarchy it links to.
	internal Vector128<byte> AsVector => throw new PlatformNotSupportedException();
	#endif
	#endif

So I would only expect this callstack for an app targeting browser, but as the comment mentions it should be trimmed and not executed since browser will fail the Sse3.IsSupported check. Something fishy is going on here, or the repro case is running binaries in a place they're not expected (eg: like building for browser and running the IL on coreCLR).

[krwq]

We'll need more info here at minimum I think following will be useful:

• csproj (at least properties and relevant nuget packages)
• how you build/publish
• how you run (i.e. is it same machine or different, what command line are you using if using dotnet tool or what output and current working directory you're using)

Currently as @ericstj mentioned stack seems a bit bogus and it's hard to tell if this is a problem with product, symbols, packaging (i.e. using wrong binary or incorrectly compiling it), trimmer or maybe JIT bug. We'll need to narrow this a bit.

I've went through list of patches on release branches from the last year and there wasn't anything which looked like it could have caused regression (unless maybe some packaging changes - I'm not an expert there so can't tell but they looked ok to me).

I've tried to repro based solely on stack trace - I tried targeting both 6.0 and 8.0 with different trimming settings but I didn't have luck getting any repro.

I used following piece of code based on stack trace:
https://github.com/dotnet/aspnetcore/blob/main/src/Servers/Kestrel/Core/src/Internal/Infrastructure/KestrelEventSource.cs#L236C1-L244C86
and
https://github.com/dotnet/aspnetcore/blob/main/src/Servers/Kestrel/Core/src/KestrelServerOptions.cs#L334-L373

I tried to wrap that with async calls tried some different combinations of properties and other random stuff I could think of (i.e. suspecting maybe trimming out strings for nameof(...) could have caused some unexpected issues but that didn't seem to be the case)

This issue has been marked needs-author-action and may be missing some important information.

[ericstj]

Agreed - we really need more repro information from the original filer. I've made the requst for more info in the VS Dev ticket, and the internal AzDo ticket. Marking this as blocked.

[tarekgh]

I pinged the reporter offline to respond to the request here. Expect some delay as he is in a different time zone.