Issue metadata
Sign in to add a comment
|
crosh runs out of memory and hangs/crashes the tab |
||||||||||||||||||||||||
Issue descriptionChrome Version: 64 Chrome OS Version: 64 Chrome OS Platform: all Network info: irrelevant (1) Ctrl + Alt + T (2) shell (3) cat /dev/urandom | hexdump (4) wait till tab crashes or hangs Expected Result: no hang or crash Actual Result: crash or hang How frequently does this problem reproduce? every time What is the impact to the user, and is there a workaround? If so, what is it? We should have non-infinite scrollback so we do not run the tab out of memory
,
Oct 30 2017
This sounds like it could be issue 757641 which was fixed mid-September I wonder if the fix is not in your version yet. You could try opening a large file as described.
,
Oct 30 2017
This was tip of tree as of last week, so if it was fixed in september, i'd expect my build to have said fix.
,
Oct 30 2017
it has always been this way. we consider this a FR rather than a bug since it's the user causing it on purpose.
,
Oct 30 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dmitrygr@google.com
, Oct 30 2017