We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
No response
External repro here: https://github.com/awphi/monaco-chrome-iframe-issue/
pnpm install && pnpm dev
Memory usage increases linearly with number of total iframes created in the page's lifespan.
Documents using monaco are not retained after its containing iframe is removed, preventing significant memory retention.
Browser Versions: Version 133.0.6943.142 (Official Build) (arm64), Version 135.0.7039.1 (Official Build) canary-dcheck (arm64) OS: MacOS 15.3.1 (24D70)
Interestingly, reducing the text length in the model (e.g. change the dummy HTML in the above repro to abc) seems to circumvent this issue.
abc
Also doesn't seem to affect FF 135.0.1 afaict
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Reproducible in vscode.dev or in VS Code Desktop?
Reproducible in the monaco editor playground?
Monaco Editor Playground Link
No response
Monaco Editor Playground Code
Reproduction Steps
pnpm install && pnpm dev
(or whatever package manager)Screen.Recording.2025-02-27.at.15.53.20.mov
Actual (Problematic) Behavior
Memory usage increases linearly with number of total iframes created in the page's lifespan.
Expected Behavior
Documents using monaco are not retained after its containing iframe is removed, preventing significant memory retention.
Additional Context
Browser Versions: Version 133.0.6943.142 (Official Build) (arm64), Version 135.0.7039.1 (Official Build) canary-dcheck (arm64)
OS: MacOS 15.3.1 (24D70)
Interestingly, reducing the text length in the model (e.g. change the dummy HTML in the above repro to
abc
) seems to circumvent this issue.Also doesn't seem to affect FF 135.0.1 afaict
The text was updated successfully, but these errors were encountered: