Browser crashing with browser history
Reported by
cryza...@gmail.com,
Aug 27 2017
|
|||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Steps to reproduce the problem:
1. Open the developer tools or just create a quick html page with the following code
var total = "";
for(var i = 0; i < 1000000000000000; i++) {
total = total + i.toString();
history.pushState(0,0, total);
}
2. Wait a second and the browser/site will crash.
3. Sometimes (Windows related) the CPU load goes even up to 100% because of the RAM management.
What is the expected behavior?
That the Site which abuses this method will immediately shutdown.
What went wrong?
The browser crashed and even the CPU load goes up 100%.
Did this work before? No
Chrome version: 60.0.3112.113 (Offizieller Build) (64-Bit) Channel: stable
OS Version: 10.0
Flash Version: 24.0.0.189 internal-not-yet-present
,
Aug 28 2017
,
Aug 28 2017
This is basically issue 394296 , and I think kinuko@'s plans in issue 672370 are what we need to prevent IPC floods / denial of service.
,
Aug 28 2017
Also, palmer's r485498 looks like it will mitigate this particular approach. |
|||
►
Sign in to add a comment |
|||
Comment 1 by brajkumar@chromium.org
, Aug 28 2017Status: Untriaged (was: Unconfirmed)