High CPU load Vivaldi processes; Vivaldi shutdown; Vivaldi don't run no more, end of the road
-
@SimBau Another possible cause would be if Vivaldi is using CPU for Graphics when your card is not fully supported; check under
vivaldi://gpu -
@SimBau said in High CPU load Vivaldi processes; Vivaldi shutdown; Vivaldi don't run no more, end of the road:
Basically the problem lay somewhere in something incompatible in my former bookmarks file. The new version would not start with my old bookmarks file, but after reverting back to 1.7.735.48 Vivaldi worked again with the bookmarks file.
My eye gravitated to this paragraph [can eyes gravitate?]. A looooooong time ago, in a
universeSS far far away, there was aprincess captured by an evil empirebug that interacted badly with prior bookmarks file versions, with the then-newer chromium version. The symptoms were entirely different to yours now, but i offer you this idea now in case it might also collaterally benefit you.- Move V's Bookmarks file from your V's Default folder, into the corresponding Default folder of any alternative chromium-based browser you have.
- In said alternative browser, Export said BM file as HTML file.
- Reopen V, Import said HTML file.
- This process reduced my Bookmarks file from 8.2 MB to 1.6 MB, & completely fixed the fault. There is a penalty however; loss of any associated Description & Nickname text you might have manually added to individual BMs. Somehow, the HTML conversion process seemed to "sanitise" the BM file, & make it fully compatible with the current chromium engine version.
Might be utterly irrelevant for you now, but just in case...
..............................................................................................
Tower & Lappy = Maui Linux 17.03 x64 Plasma 5.9.3.
.............................................................................................. -
@Ayespy
Thank you for your reply, but I do not think extensions have anything to do with this, because I have not as of yet added any extensions, I am using purely a Vivaldi installation without any additions like extensions. -
@SimBau
In case the heavy CPU load happens again click on the vivaldi menu button -->Tools--> Taskmanager. It will start vivaldis own Taskmanager so you can see what tab / webpanel / whatever is slowing you down.
I know that this isn't solving the issue with the restart but maybe this helps pinning down the resource issue. -
@zaibon
Thank you for the tip. I will try it as soon as possible. But at the moment I cannot even start Vivaldi. I am going to write a separate forum entry for the issue, but it generally involves a situation in which every day when I start my computer new, I never know if Vivaldi will run or not.
It is very bizarre: after freshly booting my computer and logging in, I double-click the Vivaldi icon and sometimes it works, sometimes it doesn't. If it doesn't, I restart the computer and try again. Sometimes that helps.
I have a procedure to ensure that no other random factors are playing a role: Right after freshly booting my computer, I don't start any other programs except for the task manager, so I can see the running processes. Then the first thing I do is double click the Vivaldi icon.
When I see four Vivialdi processes start suddenly together, then they all shortly disappear and Vivaldi won't run. But if the Vivaldi processes begin consecutively one after another, then I usually am lucky and Vivaldi starts.
I have no clue what is causing this. I haven't installed any new programs and I haven't updated my Vivaldi since 1.7.735.48 (which I am still running because of the problem I mentioned above).
This problem is becoming quite frustrating, because I like Vivaldi and use it quite a lot, especially the notes feature. -
Try to rename the Default dir in your "%localappdata%\vivaldi\user data", and while at it make a backup of it, before starting Vivaldi. If it works, then it's something wrong in your profile. It happened to some other people that some file got corrupted, and usually refreshing the profile data helps.
-
@iAN-CooG
Thank you for your tip.
I renamed the Default folder and tried starting Vivaldi and it worked. So, you say that means something is wrong with my profile? But, yesterday I used Vivaldi all day long and shut it down by clicking on the X at the top right. I didn't manually tamper with anything.
Thanks at least for helping me make some progress! -
@SimBau said in High CPU load Vivaldi processes; Vivaldi shutdown; Vivaldi don't run no more, end of the road:
@iAN-CooG
Thank you for your tip.
I renamed the Default folder and tried starting Vivaldi and it worked. So, you say that means something is wrong with my profile? But, yesterday I used Vivaldi all day long and shut it down by clicking on the X at the top right. I didn't manually tamper with anything.
Thanks at least for helping me make some progress!After renaming the Default folder Vivaldi creates a new Default folder. I shut down Vivaldi and I copied my old Bookmarks file into the new Default folder. Now Vivaldi won't start anymore.
I removed my old Bookmarks file and reverted to the new default Bookmarks file and then I tried the same thing with my Notes file: I replaced the new Notes file in the new Default folder with the Notes file from my old Default folder. Now I tried starting Vivaldi and it works.
My conclusion is that it seems like something in my Bookmarks file is causing a problem.
It is nice to narrow things down like this, but on the other hand, I don't think I am doing anything illegal with my bookmarks. I make plenty of new bookmarks every day, but they are pretty basic: pretty well every bookmark is done simply by 1. Ctrl-D; 2. select subbookmarkfolder in the dropdown; 3. Save.
It would be nice to get to the bottom of this.
-
@SimBau Good that you at least narrowed down the problem to only one file.
Now zip your Bookmarks file, upload it somewhere with a password, file a bugreport providing the zip link and password to the devs, so they can test what is the culprit. -
@SimBau You seem to have studiously ignored my post/suggestion, which deals explicitly with a corrupted Bookmarks file, & which did solve older problems for several of us who've been here a couple of years. Maybe it won't help you, but maybe it might...
-