Chromium Code Reviews| Index: chrome/test/data/prerender/prerender_excessive_memory.html |
| diff --git a/chrome/test/data/prerender/prerender_excessive_memory.html b/chrome/test/data/prerender/prerender_excessive_memory.html |
| deleted file mode 100644 |
| index 96b13f64d9aa5e18a260dfc1a05363bcc44dfca9..0000000000000000000000000000000000000000 |
| --- a/chrome/test/data/prerender/prerender_excessive_memory.html |
| +++ /dev/null |
| @@ -1,27 +0,0 @@ |
| -<html> |
|
Jói
2013/06/28 10:49:15
Why did you delete this file?
hpjonsson
2013/06/28 11:27:32
It was AVG Virus protection that did it and it esc
|
| -<!-- |
| -This test checks to make sure that a prerendered page using excessive memory |
| -is cancelled. |
| ---> |
| -<head> |
| - <title>Prerender -- Excessive Memory Use</title> |
| -</head> |
| -<body> |
| - Makes the renderer use an excessive amount of memory. |
| - <script type="text/javascript"> |
| - var string = ""; |
| - while (string.length < 1024*1024) |
| - string = string + "---------"; |
| - |
| - // This allows a sufficiently long string to be created with less copying |
| - // and reallocation of data, speeding the test and hopefully eliminating |
| - // flake. |
| - var array = []; |
| - // The maximum for the sake of this test is 30 MB, so allocate just a |
| - // little more. |
| - for (var i = 0; i < 31; ++i) |
| - array[i] = string; |
| - string = array.join(); |
| - </script> |
| -</body> |
| -</html> |