memory

[naruto1227]

When I used EFcore5 in AspNetCore5.0, I called SaveChangesAsync when I saved a field that was too long, and EFcore didn't throw an error, but the memory kept soaring

EF Core version:
Database provider: (e.g. Microsoft.EntityFrameworkCore.SqlServer)
Target framework: (e.g. .NET 5.0)
Operating system:
IDE: (e.g. Visual Studio 2019 16.3)

[roji]

Could be related to dotnet/SqlClient#593 / dotnet/SqlClient#716.

@zhanghaiboshiwo can you please try using sync I/O (SaveChanges instead of SaveChangesAsync) to check this? If it doesn't help, can you submit a minimal code sample, so we know what exactly you're doing (e.g. what is the field type, how long...)?

[naruto1227]

[naruto1227]

When I was debugging the source code, I found that the problem appeared here. When I reported an error, debugging here, the memory would soar and could not be finished

[ajcvickers]

@zhanghaiboshiwo Almost certainly a duplicate of #15214.