You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deployment completes successfully with System.Memory 4.5.5, but after updating to System.Memory 4.6.0, it never finishes and eventually fails due to a timeout.
There are no errors during the build process, and local debugging works fine.
This is a CSES application, so the framework is .NET Framework. My version is 4.7.2.
Reproduction Steps
Update System.Memory to version 4.6.0.
Deploy a CSES application on Azure.
Observe that the deployment never completes and fails due to a timeout.
Expected behavior
The CSES deployment should complete successfully without any timeout errors.
Actual behavior
CSES deployment does not complete and results in a timeout error.
Regression?
Yes, this issue does not occur with System.Memory 4.5.5.
Tagging subscribers to this area: @dotnet/area-system-memory
See info in area-owners.md if you want to be subscribed.
OgawaTakasi
changed the title
System.Memory 4.6.0 causes Cloud Service (Enhanced Support) deployment failure
System.Memory 4.6.0 causes Cloud Service (Extended Support) deployment failure
Feb 25, 2025
OgawaTakasi
changed the title
System.Memory 4.6.0 causes Cloud Service (Extended Support) deployment failure
System.Memory 4.6.0 causes Azure Cloud Services (extended support) deployment failure
Feb 25, 2025
Description
Deployment completes successfully with System.Memory 4.5.5, but after updating to System.Memory 4.6.0, it never finishes and eventually fails due to a timeout.
There are no errors during the build process, and local debugging works fine.
This is a CSES application, so the framework is .NET Framework. My version is 4.7.2.
Reproduction Steps
Expected behavior
The CSES deployment should complete successfully without any timeout errors.
Actual behavior
CSES deployment does not complete and results in a timeout error.
Regression?
Yes, this issue does not occur with System.Memory 4.5.5.
Known Workarounds
Downgrade to System.Memory 4.5.5.
Configuration
.NET Framework 4.7.2 and OS Family 6
Other information
This may be related to #109827.
The text was updated successfully, but these errors were encountered: