I have a page that always gets stuck only in chrome and safari. The page loads just fine, and then gets to 25% of the CPU (out of 4 cores - 100% if you want). He never falls, but remains immune. Safari actually says that there is an unresponsive script. I put debugging warnings on all of my startup code, and the code works very well. I have a message "waiting for www ..." that will not disappear. How can I find out what works right now? Is there a way to "reset" the current javascript stack, even if the tab is not responding?
I can’t send the link because the site is not yet ready for the general public, so if you can help with a general solution or in any way to diagnose the problem, I would really appreciate it.
Another weird thing: an unanswered page loads just fine, where it runs locally.
Any help would be appreciated.
Sonia source
share