Hallo. I have recently upgraded to Mountain Lion from Lion. I used to run Safari 6 on Lion with no major CPU issues.
Now I find that rather often after some time of multiple-tabs navigation the whole CPUs of my Macbook Aluminum 2009 are taken by the Safari Web Content Process.
Trying to debug the issue, I have discovered that it is deterministically related to javascript: I just need to disable javascript from the Developer menu in order to restore a normal CPU usage.
The effect seems to be more evident on newspaper websites (i.e. lemonde.fr, repubblica.it) that often require some javascript functionalities, but it seems tha google docs leads to similar results (high CPU usage that eventually becomes 100% usage after some time of multiple-tabs navigation).
If I stay with one unique tab, the CPU usage is steadily high but never 100% (always around 20%).
Do you suffer of the same problem? Any trick a part from disabling javascript?
Now I find that rather often after some time of multiple-tabs navigation the whole CPUs of my Macbook Aluminum 2009 are taken by the Safari Web Content Process.
Trying to debug the issue, I have discovered that it is deterministically related to javascript: I just need to disable javascript from the Developer menu in order to restore a normal CPU usage.
The effect seems to be more evident on newspaper websites (i.e. lemonde.fr, repubblica.it) that often require some javascript functionalities, but it seems tha google docs leads to similar results (high CPU usage that eventually becomes 100% usage after some time of multiple-tabs navigation).
If I stay with one unique tab, the CPU usage is steadily high but never 100% (always around 20%).
Do you suffer of the same problem? Any trick a part from disabling javascript?
