Uh oh!
There was an error while loading. Please reload this page.
Use JsonElement.Clone instead of Deserialize - #1200
Merged
Andrew Arnott (AArnott) merged 1 commit intoJun 13, 2025
Merged
Conversation
The existing code is using Deserialize to make a copy of the JsonElement in order to hold on to it past the usage of the parent JsonDocument. The problem is that the call to Deserialize isn't passing the JsonSerializerOptions. Thus when this code executes in a trimmed/aot'd app it will fail since reflection is disabled in System.Text.Json. The fix could be to pass the options into the call, but a better fix all around is to use the Clone method, which is faster than calling Deserialize<JsonElement>.
Andrew Arnott (AArnott)
commented
Jun 13, 2025
Member
/azp run |
Andrew Arnott (AArnott)
enabled auto-merge
June 13, 2025 22:09
|
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced Jan 22, 2026
This was referenced Jun 8, 2026
This was referenced Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The existing code is using Deserialize to make a copy of the JsonElement in order to hold on to it past the usage of the parent JsonDocument. The problem is that the call to Deserialize isn't passing the JsonSerializerOptions. Thus when this code executes in a trimmed/aot'd app it will fail since reflection is disabled in System.Text.Json.
The fix could be to pass the options into the call, but a better fix all around is to use the Clone method, which is faster than calling Deserialize.
cc Andrew Arnott (@AArnott)
Using this benchmark:
on my machine produces: