Snapshot 1.2.479.8 and CPU usage.
-
I've updated to "Snapshot 1.2.479.8". Don't know why, but cpu usage of this update is aweful. New page loading take 40-60% of cpu. Simple scrolling the page can take 15-30%. :blink:
-
Not just that, but the whole browser is incredibly sluggish and slow for me. Feels like I'm using some single core Atom. Something is seriously off.
-
Came to the forums today to report the same thing.
Wow, CPU usage is nuts with this version.
Didn't notice it on my personal laptop at home as it's a bit of animal, but I rather sluggish works PC is taking a major hit with this version.
So much so I've had to revert back to Chrome
-
How many of you are using the 64-bit version of Vivaldi?
-
How many of you are using the 64-bit version of Vivaldi?
I did, I uninstalled it for now and replaced it with the 32 bit version, let's see if it makes a (positive) difference.
-
How many of you are using the 64-bit version of Vivaldi?
Vivaldi 1.2.479.8 (Developer Build) (32-bit) Revision 5d484720b7ea51fccd35b8f9580e934136d87851 OS Windows Blink 537.36 (@5d484720b7ea51fccd35b8f9580e934136d87851) JavaScript V8 5.1.281.31 Flash (Disabled)
-
Same here (32-bit version), downgraded to previous build and it's much faster again.
-
I have to agree with everyone here. This new snapshot is awful, the websites are opening very slowly, the whole performance is sluggish.
-
i always use X64 on all my 4 computers.
-
Thanks for the feedback. This clarifies that it is not ONLY the X64 version, which so far has accounted for a large majority of the "slowdown" complaints, in spite of being a small minority of the numbers installed.
On my X64 Windows 10 system, for instance, 1.2.479.8 runs slick and fast. So knowing that the 32-bit version of this snapshot has some problems as well, may help the developers narrow it down and debug it.
-
Thanks for the feedback. This clarifies that it is not ONLY the X64 version, which so far has accounted for a large majority of the "slowdown" complaints, in spite of being a small minority of the numbers installed.
On my X64 Windows 10 system, for instance, 1.2.479.8 runs slick and fast. So knowing that the 32-bit version of this snapshot has some problems as well, may help the developers narrow it down and debug it.
after changing to the x86 version, I still experience these issues, albeit perhaps at a reduced rate (not sure about that).
-
Renaming your profile folder may remove the issues altogether, after which you can move the vital data from the old to the new.
Can't guarantee that. The problem could be based on system specs - my system being immune, and yours being vulnerable.
-
Renaming your profile folder may remove the issues altogether
What "profile" do you talking about?
-
The path to your profile folder (it's called "Default") is found at Menu/Help/About/Profile Path. If you rename it, the browser creates a new one, and all of your settings and data will return to a freshly-installed state. Later, if that fixed your problem, you can move critical data files like bookmarks etc. back into the newly created "Default" folder. If it doesn't help, you can delete the new one and rename the old one back again. All of this has to be done with the browser not running, of course.
-
Thanks, it helped me.
-