I have a third-party JS library that had the wrong condition to reload the page. And the page was constantly reloading because of this. I tried to find where the wrong code is.
I tried to use the Event Receiver Breakpoints method, but the comment says that you do not have a stack trace in the unload events, so it is pretty useless.
Solution that worked for me: I created a page with an iframe tag with the sandbox attribute, for example, <iframe sandbox="allow-same-origin allow-scripts allow-popups allow-forms"></iframe> and placed my site in this . This way, security errors will occur in Chrome, and the console will show where JS is trying to access the location object. You can click on it and see the code. Best of all, Chrome has a JS decompressor (the {} button in the lower left corner of the source code window), which is smart, can show a line even after beautiful printing, so you can see it even in compressed JS.
Additional information on sandbox properties: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-sandbox
Adam Wallner Apr 14 '17 at 11:21 on 2017-04-14 11:21
source share