hard to crash a project you don’t wanna see anymore? use this script!
var x = new Array(1*10E6).fill(new Array(1*10E6).fill("\0"*10E2))
console.log(x)
what it does, it makes an array with 1*10^10^10^10^10^10 arrays, and filling each array entry with 1*10^10^10^10^10^10 entries again, each on being willed with 10^10 null bytes ( “\0” )
3 Likes
it also fills up your ram, instantly
i found this while testing a new file minimizer i am writing…
i would explain why i tried this, but, a bit too complicated… for even me to usually understand
1 Like
great way to crash your pc too
2 Likes
lol,
i should probably explain…
my minimizer took up 20% of the process ram, so i tested how much it could use, and in doing so, crashed all my projects like 5+ min ago
1 Like
im guessing the assignment to the variable x
causes the ram issue
yes,
it overloads will null characters, which usually could be a random amount of bytes, and starts to fill in an array, inside of another array, causing a huge overflow, sucking up absolutely all the ram
1 Like
*** chromebook jumps to 2 %***
goodbye cruel world for about 3 hours
Dude, I’m definitely gonna try this, but not on my mobile phone.
1 Like
Don’t run this on server-side script, it stresses the Glitch project servers.
1 Like
correct it does!
i found that out the hard way yesterday
1 second later: “You account has been banned”
1 Like
yes, and i had to buy a new one
a £35 raspberry pi is probably more powerful than a chrome book…
1 Like
pro tip if you want to actually exit your node process just run process.exit()
. It doesn’t fill up glitches ram and glitch will auto reboot
Here is another glitch for you (if you can call it a glitch):
Put this code in your server.js
and your project editor will be loading forever:
exec("refresh", (error, stdout, stderr) => {
if (error) {
console.log(`error: ${error.message}`);
return;
}
if (stderr) {
console.log(`stderr: ${stderr}`);
return;
}
console.log(`stdout: ${stdout}`);
});
And also, the console will lag to death