Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[optimization] free string memory after JSON is parsed. #17479

Merged
merged 5 commits into from
Aug 1, 2024
Merged

[optimization] free string memory after JSON is parsed. #17479

merged 5 commits into from
Aug 1, 2024

Commits on Aug 1, 2024

  1. Add ExternalStringResource::freeMemory

    @dumganhar
    dumganhar committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    b3de7fc View commit details
    Browse the repository at this point in the history

  2. [optimization] free string� memory after JSON is parsed. 

    V8's garbage collector only take care of JS Heap and ignore the external string size.  So  ExternalStringResource::Dispose may be delayed which will cause memory in high value.
    @dumganhar
    dumganhar committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    df6a249 View commit details
    Browse the repository at this point in the history

  3. Remove unused code.

    @dumganhar
    dumganhar committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    37f0f33 View commit details
    Browse the repository at this point in the history

  4. Revert.

    @dumganhar
    dumganhar committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    7e723bc View commit details
    Browse the repository at this point in the history

  5. Tweak.

    @dumganhar
    dumganhar committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    8063452 View commit details
    Browse the repository at this point in the history