I would suspect an unsupported or incorrectly implemented html feature in the browser, rather than a javascript error. If I include buggy javascript on a page the page displays as it was loaded (i.e. as you would expect from the Page Source), but the scrpt just stops working (no longer modifying the page) at the point of the bug (or did not do anything at all, if it contained a syntax error), and the page won't react to mouse clicks. In the console (popping up by hitting the F12 key in FireFox, in the console tab) I can then see the error message, and the point in the javascript source code where the error occurred.
The browser message that a page crashed I only saw when I intentionally terminate the corresponding firefox.exe process with the Windows task manager. (Sometimes I have to do that, when pages try to grab more memory than is physically available, and cause my entire PC to practically grind to a halt.)
I have no Apple devices, so I don't know how to do the corresponding things in Apple browsers.
I would suspect an unsupported or incorrectly implemented html feature in the browser, rather than a javascript error. If I include buggy javascript on a page the page displays as it was loaded (i.e. as you would expect from the Page Source), but the scrpt just stops working (no longer modifying the page) at the point of the bug (or did not do anything at all, if it contained a syntax error), and the page won't react to mouse clicks. In the console (popping up by hitting the F12 key in FireFox, in the console tab) I can then see the error message, and the point in the javascript source code where the error occurred.
The browser message that a page crashed I only saw when I intentionally terminate the corresponding firefox.exe process with the Windows task manager. (Sometimes I have to do that, when pages try to grab more memory than is physically available, and cause my entire PC to practically grind to a halt.)
I have no Apple devices, so I don't know how to do the corresponding things in Apple browsers.