You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
+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.
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.The text was updated successfully, but these errors were encountered: