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
The CsdlReader.TryParse does not throw an exception when parsing CSDL document with missing xmlns=”http://docs.oasis-open.org/odata/ns/edm”. Instead, the memory continuously increases until it reaches the maximum limit, resulting in significant memory usage. This condition persists until the operation is either forcibly stopped, canceled, or time out.
Schema without xmlns="http://docs.oasis-open.org/odata/ns/edm" should throw an exception or should be captured as part of EdmError instead of running to forever and increases memory usage.
Actual result
The memory continuously increases until it reaches the maximum limit, resulting in significant memory usage. This condition persists until the operation is either forcibly stopped, canceled, or time out.
Additional detail
Optional, details of the root cause if known. Delete this section if you have no additional details to add.
The text was updated successfully, but these errors were encountered:
The
CsdlReader.TryParse
does not throw an exception when parsing CSDL document with missingxmlns=”http://docs.oasis-open.org/odata/ns/edm”
. Instead, the memory continuously increases until it reaches the maximum limit, resulting in significant memory usage. This condition persists until the operation is either forcibly stopped, canceled, or time out.Assemblies affected
Microsoft.OData.Edm 7.x, 8.x
Reproduce steps
Clone the repo: https://github.com/WanjohiSammy/MemoryLeakInCSDLReaderTryParse.git
Run the application:
xmlns="http://docs.oasis-open.org/odata/ns/edm"
from theSchema
tag and run the applicationVisual Studio Diagnostics Tools
<Schema xmlns=""http://docs.oasis-open.org/odata/ns/edm"" Namespace=""NS"">
, the CSDL document is parsed successfullyExpected result
Schema without
xmlns="http://docs.oasis-open.org/odata/ns/edm"
should throw an exception or should be captured as part ofEdmError
instead of running to forever and increases memory usage.Actual result
The memory continuously increases until it reaches the maximum limit, resulting in significant memory usage. This condition persists until the operation is either forcibly stopped, canceled, or time out.
Additional detail
Optional, details of the root cause if known. Delete this section if you have no additional details to add.
The text was updated successfully, but these errors were encountered: