V 6.6 | Slow Performance Since Upgrade?
-
@Ayespy You don't know for sure that it's not the same cause Maybe it is, maybe it is not.
-
@vivaldibecameSLOW The structure of Vivaldi has changed completely since then. And the solution that fixed it in 2019 would no longer apply to the current issue.
-
@BenziJunior somebody mentioned it in the thread before, but I can confirm that there is no performance issue when opening a new private window. While the non-private Vivaldi windows are still slow, the private window is snappy. I haven't tried to use that new private window for a long time to see if it would eventually slow down, though.
-
@Ayespy Again, you don't know for sure that it's not the same cause. Have you read the code? What was the cause?
And please share some details about the solution that fixed it in 2019, because I don't see any shared in the thread (thread in which other users complain about the same issue in messages from 2020, 2021, and in other threads in 2022, 2023 and now 2024 )
-
@vivaldibecameSLOW It's computer programming common sense at work. Any sort of resource management issue in the "extension" that makes up Vivaldi's UI could cause a gradual slowdown, and there's likely to be umpteen billion different candidates for that sort of thing. It's not a "find the one thing causing this and just solve it already" type of situation. By even attempting to imply that this is a specific problem that has been around for five years (which it sure as heck hasn't been for me, although it very much is an issue now) all you're doing is throwing around unhelpful accusations. It's not contributing to actually solving the problem being faced now.
-
@Viqsi And you are 100% sure how? Please show me the previous fix for the slow-down performance issue
All I'm saying is: we do not know if that was the same cause or not. And this is factually correct, unless you show me the cause & fix for the problem in the 2019 thread
And I'm a software engineer, I know what is and isn't programming common sense
And don't say I'm "throwing unhelpful accusations". My first message was just a link to the same problem happening in 2019, which could have given some hints to the developer team as to why it's still happening / happening again. I don't care if it's the same cause or not, it's the other dude who started confidently ranting about that, while having no proof
-
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
@vivaldibecameSLOW It's computer programming common sense at work. Any sort of resource management issue in the "extension" that makes up Vivaldi's UI could cause a gradual slowdown, and there's likely to be umpteen billion different candidates for that sort of thing. It's not a "find the one thing causing this and just solve it already" type of situation
@vivaldibecameSLOW said in V 6.6 | Slow Performance Since Upgrade?:
And don't say I'm "throwing unhelpful accusations". My first message was just a link to the same problem happening in 2019, which could have given some hints to the developer team as to why it's still happening / happening again.
Guys, let's not make this a thing. I understand both of you, vivaldibecameSLOW is just trying to help. But this might as well have been a different issue, and Vivaldi v2 is quite old and I can't remember having these type of problems with any other Vivaldi version except for 6.2+. I'm sure the Vivaldi developers will be able to figure it out where the problem may lie in the resource management area, no need for another discussion. Let's remain focused.
-
I have read very few of the posts in this thread and am only writing because I have recently noticed that Vivaldi has actually become very slow.
The pages of my wordpress blog are all cached and therefore load very quickly.
In Opera, for example, they load immediately in a fraction of a second, whereas in Vivaldi it sometimes takes up to just under half a second. So Opera is several times faster.
I could imagine that there was - without conscious manipulation - a cache purging not long ago. Maybe the browser cache didn't work as fast as it should.
I also trust that it will be fixed soon. -
Possibly interesting detail - when bringing up the devtools console on those windows that I've been opening and closing a lot of tabs in (using vivaldi://inspect/#apps ), I've noticed that there's a whole heck of a lot of Javascript errors. By far the most common:
<webview>: Script cannot be injected into content until the page has loaded. webViewImpl.executeCode @ extensions::webView:242
Also frequently showing up:
Unchecked runtime.lastError: Cannot access contents of url "<URL>". Extension manifest must request permission to access this host.
(with <URL> replaced with the URI of some page I was browsing at the time).I also get the occasional
Unchecked runtime.lastError: The tab was closed.
andUnchecked runtime.lastError: Unknown error.
, and there's at least oneUnchecked runtime.lastError: Could not find guest
.I'm not sure how helpful or diagnostic any of this is, but it struck me as potentially useful as a visible symptom that's slightly more observable than "it just gets slow".
-
Oh, and there's another instance of that extension with no tabs seemingly associated with it (main thread?) and it's got a lot of interesting entries.
Promise from PrefsCache resolved in 40 ms vendor-bundle.js:1 Promise from VivaldiFeatureFlags resolved in 43 ms vendor-bundle.js:1 Promise from vivaldiSettings resolved in 197 ms vendor-bundle.js:1 Promise from ProxyActions.loadPlatformSupport resolved in 0 ms vendor-bundle.js:1 Promise from WindowActions resolved in 104 ms vendor-bundle.js:1 Promise from ThemeActions resolved in 4 ms vendor-bundle.js:1 Promise from SearchEngineCache resolved in 109 ms bundle.js:1 Non-promise from ReadingListActions with time 0 ms bundle.js:1 Non-promise from SearchFieldActions with time 0 ms vendor-bundle.js:1 Promise from WorkspaceActions resolved in 20 ms vendor-bundle.js:1 Promise from WorkspaceLinkRoutingActions resolved in 19 ms vendor-bundle.js:1 Promise from PeriodicReloadActions resolved in 18 ms vendor-bundle.js:1 Promise from HueActions resolved in 16 ms vendor-bundle.js:1 Promise from SyncedTabsActions resolved in 13 ms vendor-bundle.js:1 Promise from CommandActions resolved in 8 ms vendor-bundle.js:1 Promise from ContentScriptActions resolved in 398 ms vendor-bundle.js:1 Promise from Menu resolved in 398 ms vendor-bundle.js:1 Promise from NoteActions resolved in 398 ms vendor-bundle.js:1 Promise from SyncActions resolved in 398 ms vendor-bundle.js:1 Promise from VivaldiAccountActions resolved in 402 ms vendor-bundle.js:1 Promise from ProxyActions resolved in 400 ms vendor-bundle.js:1 Promise from DownloadActions resolved in 399 ms vendor-bundle.js:1 Promise from HistoryActions resolved in 827 ms vendor-bundle.js:1 Promise from SessionActions resolved in 826 ms vendor-bundle.js:1 Promise from Mail resolved in 824 ms vendor-bundle.js:1 Promise from TrashActions resolved in 833 ms 103Third-party cookie will be blocked. Learn more in the Issues tab. vendor-bundle.js:1 Promise from BookmarkActions resolved in 2138 ms vendor-bundle.js:1 Promise from DirectMatchActions resolved in 2621 ms bundle.js:1 Non-promise from updateJumplist with time 0 ms bundle.js:1 JS init startup: 4076.0380859375 ms bundle.js:1 Uncaught (in promise) Error: No tab with id: 74856323. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74889097. bundle.js:1 Uncaught (in promise) Error: No window with id: 74889095. main.html:1 Uncaught (in promise) Error: No tab with id: 74881698. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74901378. bundle.js:1 Uncaught (in promise) Error: No window with id: 74901373. bundle.js:1 PageStore.activatePage: page to activate not found (anonymous) @ bundle.js:1 bundle.js:1 Uncaught (in promise) Error: No tab with id: 74907151. main.html:1 Uncaught (in promise) Error: Failed to find a tab with id 74907145 bundle.js:1 Uncaught (in promise) Error: No tab with id: 74937538. bundle.js:1 Uncaught (in promise) Error: No window with id: 74937534. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74941746. bundle.js:1 Uncaught (in promise) Error: No window with id: 74855119. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74979793. 4bundle.js:1 Uncaught (in promise) Error: No tab with id: 74987122. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74997883. bundle.js:1 Uncaught (in promise) Error: No window with id: 74979797. main.html:1 Uncaught (in promise) Error: No tab with id: 74857190. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74997903. bundle.js:1 Uncaught (in promise) Error: No window with id: 74855126. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74998413. bundle.js:1 Uncaught (in promise) Error: No window with id: 74938491. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74998427. bundle.js:1 Uncaught (in promise) Error: No window with id: 74855082. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74998644. bundle.js:1 Uncaught (in promise) Error: No window with id: 74855116. bundle.js:1 Uncaught (in promise) Error: No tab with id: 74998648. bundle.js:1 Uncaught (in promise) Error: No window with id: 74979239. 2bundle.js:1 Uncaught (in promise) Error: No window with id: 74855100. bundle.js:1 Attempt to show another context menu while one is initializing D @ bundle.js:1 bundle.js:1 Uncaught (in promise) Error: No window with id: 74855100.
(sorry if it's hard to read; copy-paste doesn't work very well in the console)
-
Meanwhile, I tried something a little unusual - having noticed that one window (in which I'd been opening and closing a lot of tabs) with a lot of errors, I tried closing it and then restoring it from Recently Closed Tabs. The UX was really really slow to pop up the Recently Closed Tabs menu, but after restoring the window... suddenly Vivaldi is back to being zippy.
It's still generating those error messages in the console as I open new tabs, though:
I may take some time later and see if I can find out if disabling things makes those errors stop showing up. If they really are correlated to the slowdown, then that would be a very helpful discovery.
-
This might be more useful. Opened a single tab in that same window and got what looks like a traceback (albeit with obfuscated function names).
-
Bonus tip: the "zippiness restoration by closing/reopening windows" workaround mentioned earlier is a lot cleaner and faster if done by making use of Workspaces. (I hadn't been. I am now.)
I'ma keep trying that for a while longer and see if it's a consistent workaround. If it is, 1) that makes this a less pressing issue for me and 2) that narrows things down nicely.
-
@magilex said in V 6.6 | Slow Performance Since Upgrade?:
Following up, I did have some slow down yesterday, similar to before where tabs get "stuck" and remain in place when closed, opening new tabs does not happen, or is sluggish.
New for this version is this behaviour recovered itself and I did not have to restart the browser yet, so it looks like something has improved, but not fully.Will see how this progresses over the next few days.
I was resigned to having to restart daily before, along with having to kill the processes in task manager that do not close off on closing the application.
FYI, my home laptop is running 6.5.3206.59 under Ubuntu 22.04 & I've also gotten the same behavior where a tab will get 'stuck' open and nothing works short of killing all vivaldi processes. (Actually wrote a script to do it for me when this happens.) When it happens, I cannot open a new tab, close existing tabs, close the browser, open the menu - nothing. I can switch between existing tabs, but not move to different pages inside of those tabs.
Frankly, I never connected this intermittent issue with the upgrade of Vivaldi, but thinking back, that's about when it began. Doesn't happen often - maybe once a week or so - but is HIGHLY confusing / annoying when it does.
Just my $0.02 in the hope that knowing it's happening on a Linux OS will be of assistance in tracking down the source of this issue.
-
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
Possibly interesting detail - when bringing up the devtools console on those windows that I've been opening and closing a lot of tabs in (using vivaldi://inspect/#apps ), I've noticed that there's a whole heck of a lot of Javascript errors.
I'm not sure how helpful or diagnostic any of this is, but it struck me as potentially useful as a visible symptom that's slightly more observable than "it just gets slow".
I didn't know about vivaldi://inspect/, but I'm not seeing any of these errors, or do you need to click on inspect with each website?
But I do have to say that I'm currently running Vivaldi 6.1 for 7 days (full week), without any slowdown at all, even after opening and closing many tabs. And it also exits in one second, without any hanging in memory problem.
So there clearly is a difference between 6.1 and all newer versions, we're not imagining things, that's for sure. And it's with the exact same configuration (bookmarks, extensions) and with the exact same third party security tools (and Windows Defender). The problem must be in Vivaldi 6.6 itself, there is no doubt.
@BenziJunior said in V 6.6 | Slow Performance Since Upgrade?:
As a member of the team, I am aware but not been able to reproduce the issue. Haven't had time to go through the original thread as I'm working on other performance related tasks, but will try to investigate further once I have more time.
I wonder if the developer BenziJunior has already looked at stuff?
-
Suggestion for those trying to reproduce the issue but not seeing it (so, for example, @mib2berlin ) - when opening and closing tabs, try doing so not by just opening and closing empty tabs, but opening links to other pages in new tabs. If I open an empty new tab and then go to some site in same, or if I unhibernate a hibernated tab, I don't get any console errors, but if I middle-click on a link to open in a new tab, the console errors show up.
-
@Viqsi
Hi, I test this with open bookmark folders with 20-30 bookmarks.
It were impossible for me to open/close 1000 tabs a day with my regular workflow, open link, back gesture, open next link and so forth.
I can check console errors at weekend.Cheers, mib
-
ZZalex108 forked this topic on
-
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
Suggestion for those trying to reproduce the issue but not seeing it (so, for example, @mib2berlin ) - when opening and closing tabs, try doing so not by just opening and closing empty tabs, but opening links to other pages in new tabs. If I open an empty new tab and then go to some site in same, or if I unhibernate a hibernated tab, I don't get any console errors, but if I middle-click on a link to open in a new tab, the console errors show up.
I did forget to mention that this is indeed the way that I mostly browse the web. So I often open some website, and then via middle click I open multiple links in the background and then I stack those tabs per domain-name. Perhaps this somehow also plays a role. But to clarify, I don't know how to reproduce the console errors.
-
@SwiftyPop 'Clean Site Data'-link (page= https://help.vivaldi.com/desktop/tools/delete-browsing-data/#:~:text=Delete Password.-,Delete data per website,-Option 1) has some kind of bookmark in it, so better just use https://help.vivaldi.com/desktop/tools/delete-browsing-data/
-
The windows "efficiency" mode was wrecking my vivaldi performance. And it seems windows updates can change things around making the issue better or worse at times.
For everyone that didn't try still, check the first post for the flag to disable this moronic windows feature in vivaldi.