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.

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

Simulate low memory or throttle memory like how DevTools can throttle CPU #12

Open
zoherghadyali opened this issue Mar 8, 2022 · 3 comments
Labels
feature New feature or request

Comments

@zoherghadyali
Copy link
Collaborator

When debugging an issue that only reproduces in low memory environments, DevTools should have the ability to simulate low memory or throttle memory. DevTools can already throttle CPU to mimic slow performance and it'd be useful for memory debugging to be able to do the same.

From List of V8 flags, V8 has a flag called --max-old-space-size that appears to constrain the memory usage of a tab in the browser when specified via --js-flags but we should continue to investigate if this actually simulates low memory or if the tab has the same virtualized memory it would normally have.

@zoherghadyali zoherghadyali added the feature New feature or request label Mar 8, 2022
@tkadlec
Copy link

tkadlec commented Mar 31, 2022

Ooo....didn't know about this flag! SUPER interested here as I think exposing a way to simulate low-memory situations in WebPageTest would be fun too.

@samdenty
Copy link

samdenty commented Dec 2, 2024

+1 to this

@j-osephlong
Copy link

+1 To this. On Chrome Android, there is an issue that some face when uploading images where they get the error "unable to complete previous operation due to low memory". This can be hard to debug but if we had the ability apply memory constraints with dev tools it could help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants