V 6.6 | Slow Performance Since Upgrade?
-
@vivaldibecameSLOW said in V 6.6 | Slow Performance Since Upgrade?:
Vivaldi is riddled with bugs and performance issues...
I find this to be untrue. I never have a performance issue, and rarely encounter a bug. I test for bugs daily, but find one to file a report on, only once every few months.
I suppose a good deal depends on equipment, extensions, modifications and usage
-
@Ayespy Now that you mention equipment, this slow behavior when opening new link or tabs (10sec to load) only happen in Windows 10 enviroment and is not all the time, sometimes is fast sometimes laggy but when I use Vivaldi in MacOS always it feels fast to load everything.
-
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
I'm more convinced than ever that there is some sort of resource leak in the Vivaldi window UX that is responsible for the slowdowns, and I still believe it is tied to tab creation/deletion management because the "problem windows" that I keep closing-and-reopening are the ones where I open-link-in-new-tab more often than not.
OK thanks for the feedback. Major bummer that it still hasn't been fixed. And also no response from any developer. I'm still on Vivaldi 6.1, which works just fine, but eventually I would like to be able to upgrade to newer Vivaldi versions on my current machines.
-
Oh thankfully i am not the only one....having serious lag issues as well!
I run on 6.6.3271.61 (Stable channel) (64-bit) and i didnt try any other workarounds you suggest, as it seems that they dont work for the majority of you!
PS: I restart my laptop daily!
-
One thing to remember is that an issue like the one described here is very difficult to analyze, because it takes so long for the problem to develop (E.g. I may be seeing the same/similar issue, but it only becomes noticeable after several days, maybe over a week of running the same instance of Vivaldi)
Running in a debug environment for that kind of time period is not really practical, unfortunately. Unless we have an inkling of where the issue is (and can instrument it), we essentially need steps that can reproduce the issue relatively quickly (which often means much less than an hour), and I suspect that is not really practical in this case, either.
Another thing to keep in mind is that details such as what features you are using, e.g. Mail, extensions, other configuration choices, other usage factors (e.g. tab usage patterns), may play a part. In my quick skim just now, I noticed a number of posts that did not seem to include such information (in some cases there may be information, but hidden inside a lot of other text. Pro Tip: Using short bullet point descriptions to list information is very useful).
Knowing that kind of information may help discover what is, and (in particular) what isn't, involved in creating the problem, which may help narrow down where to look for the problem. (E.g. I have Mail enabled, no extensions, only minor configuration changes, and opens some multi-bookmark entries at least once a day, which is usually how I notice the problem, I always close tabs after reading, which creates a long history of closed tabs, which may conceivably be related to the cause of the problem.)
Regarding opening in other profiles and Private Window not being affected, the reason and important part there is that those are running in completely different, separate processes than the main profile and window(s), so they are isolated from whatever is affecting the main profile.
BTW, @RasheedHolland, you may want to check back on who you have been replying to in this thread; you were actually replied to by, and replying to, a Vivaldi dev over a month ago.
-
@yngve said in V 6.6 | Slow Performance Since Upgrade?:
"...it takes so long for the problem to develop..."
And that's assuming it does somehow develop. I basically never turn off my machine or close my browser (except to update) and it never develops.
I set up hundreds of tabs and infinite history in a stable instance and ran it for a month, and the problem never developed.
How to get it to happen - at all - is definitely not a given.
-
Posting from Firefox while I wait for Vivaldi to wake up.
I don't have much to add other than my observation that this appears more as Vivaldi postponing things rather than sluggishness. I ask it to open a link, when it doesn't, I click on another tab to see if it will respond, do some other stuff it doesn't respond to and then a while it later it will simply respond to everything.
My problems also began with 6.2 if I am recalling correctly. At the moment they are quite reproducible. I have to blow Vivaldi away and restart four or five times a day every day.
I'm going to revert to 6.1. Before I do that is there anything I should do to make this a more productive diagnostic?
In the absence of advice I'll just do the obvious, revert and report back on whether the issue changes.
-
@KlausFranbrau2
Hi, first you should never downgrade Vivaldi, you get a broken profile and this can cause such issues.
Install Vivaldi as standalone, import bookmarks and passwords or use sync to get it in a working state and test this.
Check your security software if it is running high CPU if you use Vivaldi.Me, some customers and friends use Vivaldi without any problems, my phone would ring very quickly if someone had a problem with Vivaldi.
I run test with 700-1000 tabs for several days up to a week and get no lagging at all on Vivaldi 6.4, 6.5, Windows 11.
I give up to test this again.
Something on your system and others slowdown Vivaldi but nobody know what and why. -
@yngve said in V 6.6 | Slow Performance Since Upgrade?:
One thing to remember is that an issue like the one described here is very difficult to analyze, because it takes so long for the problem to develop (E.g. I may be seeing the same/similar issue, but it only becomes noticeable after several days, maybe over a week of running the same instance of Vivaldi)
But what do you think about the feedback from Viqsi, who believes it might be a bug in Vivaldi's resource management? Could you guys not simply look into the differences in this area when it comes to Viv 6.1 and 6.2/6.6? Because this problem started with Viv 6.2, which was a major redesign.
https://news.itsfoss.com/vivaldi-6-2-release/
BTW, @RasheedHolland, you may want to check back on who you have been replying to in this thread; you were actually replied to by, and replying to, a Vivaldi dev over a month ago.
Yes correct, but he hasn't been active in this thread anymore after that, that's what I meant. So I haven't got a clue if he at least tried to look into this problem and what his findings were. BTW, are you a developer too?
-
@RasheedHolland said in V 6.6 | Slow Performance Since Upgrade?:
Could you guys not simply look into the differences in this area when it comes to Viv 6.1 and 6.2/6.6?
The problem with doing that is in part, that just between the branchoff for 6.1 to the change over to v6.3 (when we released 6.2), there are 800+ changes in the Vivaldi code, in 2300 files; many of those are not relevant, but even just counting the Vivaldi UI, there are 730+ files modified in 400+ updates.
And that is before one counts in all the chromium changes during that time, and the Chromium team typically adds several hundred updates each day (and there are about 60 days between each update....), and additionally there is likely a similar number of updates in the Javascript engine (V8) on which our UI depends.
My point is not just that there are a lot of updates, but that without knowing what to look for, finding that proverbial real needle in the real haystack would be real easy.
One way that we might be able to narrow the search down is to know that Snapshot/Build A worked fine, while the next Snapshot/Build B have the problem (this can be accomplished using a method called bisection, check midway between a known good build and a known bad build, afterwards you know if that middle build is a known good build or a known bad one, repeat with the new boundaries, 1000 builds can be cleared in about 10 tests). With that kind of boundary, we can narrow the search down quite a lot. For example, if Build A is before a major Chromium update, while build B is after, the Chromium update is something one would have to look more closely at, but the "reduced" haystack just grew quite a lot bigger.
That there is a possible issue with memory management seems likely, based on what I have seen during shutdowns. But whether that is caused by something in Vivaldi's UI, or something more fundamental in the Chromium V8 engine (which handles the memory management) is something that is not possible to say at this time.
-
@RasheedHolland @yngve is a developer.
-
As I said, I'm about to revert, so perhaps I could help with that bisection.
I do want to be rid of the bug for a while so I would be wondering if you have a suggestion for what build would be most likely to be right before anyone reported this.
Later I could then advance to the first suspected build.
-
@KlausFranbrau2 said in V 6.6 | Slow Performance Since Upgrade?:
I'm about to revert,
Don't revert in place, that is asking for trouble; new installation and profile directories are needed, and you can use sync to transfer data.
-
@KlausFranbrau2 It is not advisable to run on old versions, except for testing. Just too many potential security problems.
I don't know if I have any real information, beyond a couple of pieces: 6.1 is supposed to work fine, 6.2 is supposed to have issues, and there was a chromium update to 116 a few weeks before 6.2 was released.
-
6.1 Final is https://vivaldi.com/blog/desktop/6-1-rc-2/
-
First 6.2 snapshot was https://vivaldi.com/blog/desktop/catch-up-vivaldi-browser-snapshot-3054-3/
-
The snapshot before default enabling Portals was https://vivaldi.com/blog/desktop/another-round-of-fixes-vivaldi-browser-snapshot-3060-3/ [1]
-
The last 6.2 snapshot based on Chromium 114 was https://vivaldi.com/blog/desktop/same-old-new-window-now-opens-faster-vivaldi-browser-snapshot-3062-3/ , which is also the one that enabled Portal windows by default [2]
-
The first Chromium 116-based snapshot was https://vivaldi.com/blog/desktop/macos-geolocation-and-customizable-address-suggestions-snapshot-3070-3/ [3]
-
6.2 final was https://vivaldi.com/blog/desktop/6-2-rc-2/
Of these, the ones I tagged [1], [2], and [3] may be the most likely regression points. Given that Portals was an Experiment, it is possible to enable it in [1], and AFAIK disable it in [2] and likely for a while longer.
While determining a breakage in [2] will only determine the feature responsible; the actual code involved was under development for months prior to that release, that might help guide an investigation.
-
-
Good news, I think (fingers crossed) that the problem has been solved for me. I believe the fix was a recent update to the driver of my Intel integrated graphics card (31.0.101.5382, release date: 29th March 2024).
Try to update your drivers and see if that helps.
-
@yngve said in V 6.6 | Slow Performance Since Upgrade?:
@RasheedHolland said in V 6.6 | Slow Performance Since Upgrade?:
That there is a possible issue with memory management seems likely, based on what I have seen during shutdowns. But whether that is caused by something in Vivaldi's UI, or something more fundamental in the Chromium V8 engine (which handles the memory management) is something that is not possible to say at this time.
OK thanks for the feedback, I now understand it better why it's so hard to pinpoint this problem.
And yes, I have never seen Vivaldi hanging in memory before, it all started with 6.4 (I upgraded directly from 6.1 to 6.4) but people have been complaining about performance degradation and Vivaldi not being able to exit memory instantly since 6.2 apparently. It usually takes around 5 to 10 minutes to exit from memory. And this only happens after Vivaldi 6.4+ has been active in memory for a couple of hours and probably also if quite a lot of tabs are open.
I have tested it with Process Monitor and no third party app/process seems to be involved with this problem. It's really a shame because I can't upgrade 6.1 because of this issue. Also, can you perhaps take a look at this bug (see link), this is another reason why I can't upgrade to 6.7, this bug has been present since 6.4, should be easy to fix I suppose.
https://forum.vivaldi.net/topic/95696/6-6-bookmarks-nicknames-not-working-in-url-bar
-
@vivaldibecameSLOW said in V 6.6 | Slow Performance Since Upgrade?:
Good news, I think (fingers crossed) that the problem has been solved for me. I believe the fix was a recent update to the driver of my Intel integrated graphics card (31.0.101.5382, release date: 29th March 2024).
Try to update your drivers and see if that helps.
Wow, I would be really surprised if this was the fix for the problem. But the thing is, people who have reported this were all using different GPU's, so I don't see how this would be the issue. Also, I have a laptop with both an Intel UHD GPU and a Nvidia GeForce GPU, which would mean that if I force Vivaldi to use the Nvidia GPU, it should also be possibly solved? I mean without me having to upgrade my Intel UHD GPU drivers?
-
@RasheedHolland I'm surprised as well, but it was right after I updated the driver that Vivaldi didn't slow down after a certain time anymore. I also have a Nvidia GPU + Intel integrated graphics. If I remember correctly, I had already tried in the past to force Vivaldi to use the GPU but it didn't solve the problem (though I'm not sure if I did correctly).
Just upgrade your Intel integrated graphics' driver, it's worth a try!
-
@RasheedHolland said in V 6.6 | Slow Performance Since Upgrade?:
I don't see how this would be the issue.
There is probably no such thing as "THE" issue. There are probably a range of completely different issues with similar symptoms experienced by different people and complained of as the "same" thing.
-
@vivaldibecameSLOW said in V 6.6 | Slow Performance Since Upgrade?:
@RasheedHolland I'm surprised as well, but it was right after I updated the driver that Vivaldi didn't slow down after a certain time anymore. I also have a Nvidia GPU + Intel integrated graphics. If I remember correctly, I had already tried in the past to force Vivaldi to use the GPU but it didn't solve the problem (though I'm not sure if I did correctly).
Just upgrade your Intel integrated graphics' driver, it's worth a try!
I guess it's worth a try, but I don't want to mess things up so that I have to reinstall Windows all over again, it takes too much time. And from a technical point of view, I wonder how the GPU can play a role, and why does it only happen with Vivaldi? Shouldn't this then be fixed in Vivaldi, know what I mean?