Answer the question
In order to leave comments, you need to log in
JS in Chrome started to freeze, what is the reason?
Just a few days ago, chrome started behaving strangely. More precisely, oddities appear in the drop-down elements on the pages. Not on all sites, but, for example, sites with bootstrap 2.3, drop-down Collapse blocks. You press on the control and only after 5 seconds the block opens. There is no content upload. In the console, it shows that the class that is responsible for displaying the block is assigned immediately after clicking on the control. But the block itself will appear after 5 seconds. I tried to follow the code, but did not understand where it stops - the whole code is executed, but at the end of the function everything freezes. The Collapse block behaves the same way on bootstrap's offsite. By the way, everything is fine with Collapse in bootstrap version 3.
TweetDeck behaves just as slow in the browser, although it works fine as a separate application. The brakes are released if you need to open a tweet in a column - you press and only after 5 seconds the tweet is opened, which is strange, the browser does not freeze, because all other elements of the page are active: you can scroll through the columns, hover events all work, that is, the site is active.
It is clear that in order to understand what is happening, you must at least understand the mechanisms of JS bootstrap and TweetDeck - this is not even the question. Is it possible to reinstall javamachine or what is responsible for executing JS? Because neither disabling all plugins, nor clearing the cache, nor completely reinstalling Chrome helped, it works the same with the --no-sandbox parameter. I can’t understand why this is so, because just a couple of days ago everything worked like clockwork.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question