storage - do not eager parse extension storage (fix #163446) #166281
Merged
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.
This is for #163446. As it turns out, the storage service will not do any
JSON.parseeagerly. Storage values are primitives but never objects. However, we seem to be doing someJSON.parsefrom here specifically for extensions:vscode/src/vs/platform/extensionManagement/common/extensionStorage.ts
Line 151 in 5f383ab
I tried to reduce calls to this method in the renderer in favour of the new
getExtensionStateRawand move the parsing to the extension host to avoid large stalls in the renderer. In addition, I am logging a warning when an extension storage value exceeds 500kb.@sandy081 there are still some calls to
getExtensionStatein your area which are probably needed but I think they also happen from another process?//cc @alexdima