Extremely slow performance since upgrade
-
Hi! I'm on Linux (i5-10500T/8GB ram/Intel 630 graphics) and I also experience this annoying tab slowdown lag after about a day of usage. About 15-20 open tabs and private window for my reddit porn account always open.
This crap started with 6.2 and continues on 6.5. Plus address bar and tab font is weird tiny since 6.2 and I can't find any way to make font bigger like it was on 6.1. -
I can't be bothered to read 16 pages of posts, but I'd like to add my experience. Vivaldi gets unbearably slow after using it for approximately a week, and it only gets worse from there. It seems to be some kind of a memory/resource leak as it gets worse over time. I usually have two browser windows with a total of around 100 tabs open, most of which are not loaded (lazy load). I use a lot of YouTube and Twitch on this PC if that makes a difference. It's not completely unreasonable to restart my browser once a week, but this clearly indicates some kind of bug/problem in the browser. Is there anything I can do to help debug this?
Windows 10, i5-3570k, 32GB RAM, RTX 3070
-
@ntoskrnl You can run all (all, not most, or the most reasonable) troubleshooting steps from https://help.vivaldi.com/desktop/troubleshoot/troubleshooting-issues/ and report results here...
-
@Ayespy Thanks for the reply. I think the most reasonable/relevant steps from the list are "restart browser" and "disable extensions".
As said, restarting fixes the issue temporarily, until the browser gets slow again.
Extensions are trickier, because I cannot go a week without extensions to perform the test. I do have some extensions which are potentially heavy, but I've never had issues on another PC with Chrome with the same extensions. But my usage patterns are quite different between PCs which could be a factor.
Is there a way to narrow down the problem to a specific tab or extension or browser component using the task manager or some other developer tools? I wish I could do the debugging right now, but I only have an uptime of 3 days because of Windows updates.
-
@ntoskrnl Performing all the tests IS what narrows down the possible causes. Troubleshooting is an empirical process. If one does not rule out possible causes, testing cannot proceed.
Nothing necessarily has to be done over a long period of time. One can try a couple of days of virgin profile for instance, or a couple of days of running "naked" (no 3rd party security software), but one simply cannot omit even one troubleshooting step altogether.
-
@Ayespy I understand where you're coming from, but in my opinion it's worth understanding what we're dealing with to narrow down what we need to test. For example, we know that enabling 3rd party cookies is not going to fix this, so it's unnecessary to test that. We wouldn't learn anything from such a test.
I'm not sure why you say that nothing necessarily has to be done over a long period of time. This issue is only apparent after 1 week or more of using the browser every day.
I went through all the tests in the list and here are my thoughts:
- Restart the browser: N/A
- Make sure the browser is up to date: Up to date
- Test in a different profile, Reset settings, Test in another browser: These three are essentially the same. Relevant
- Disable Extensions: Relevant
- Enable (Third-Party) Cookies: Not relevant
- Disable Tracker and Ad blocker: Inbuilt blocker already disabled
- Delete Browsing Data: Not relevant
- Disable Hardware Acceleration: Not relevant (problem would occur immediately, not after a week, if this was the problem)
- Change the reported User Agent: Not relevant
- Check your security software: Only Windows Defender with default settings
The only two relevant tests are 1) disabling extensions and 2) resetting browser settings. Test 1 would tell us if the problem is in an extension or the browser itself. Test 2 would tell us if there's a specific browser setting that I have enabled but is disabled by default that's problematic.
I'm not going to perform either test, because in practice I can't use my browser without extensions or custom settings for a week or more, even if it's technically possible.
Instead, I'm asking for tips on how I could find out which website/tab, extension or browser component has leaked resources when the issue actually happens. I'm sure this must be possible somehow. If I had already narrowed this down to a specific website, extension or browser component, how would the developer of that website/component debug it?
-
@ntoskrnl said in Extremely slow performance since upgrade:
I can't be bothered to read 16 pages of posts, but I'd like to add my experience. Vivaldi gets unbearably slow after using it for approximately a week, and it only gets worse from there. It's not completely unreasonable to restart my browser once a week, but this clearly indicates some kind of bug/problem in the browser. Is there anything I can do to help debug this?
The question is, do you also get this with Vivaldi 6.1? And to be honest, when your browser is open a week, it's not weird that it will start to become more sluggish. The problems that are reported in this thread, are more about Vivaldi 6.4/6.5 getting sluggish after only 24+ hours or so, which is out of the ordinary. Viv 6.1 runs just fine, even after a couple of days in memory. Also, when you close Viv 6.5 after a week, will it hang in memory? You can check this with a tool like Process Explorer.
-
@funeralium said in Extremely slow performance since upgrade:
Hi! I'm on Linux (i5-10500T/8GB ram/Intel 630 graphics) and I also experience this annoying tab slowdown lag after about a day of usage. About 15-20 open tabs and private window for my reddit porn account always open. This crap started with 6.2 and continues on 6.5. Plus address bar and tab font is weird tiny since 6.2 and I can't find any way to make font bigger like it was on 6.1.
OK, so when you return to Vivaldi 6.1, all is fine? And when you search for Zoom in Vivaldi's Settings, you should be able to zoom the interface.
-
@RasheedHolland said in Extremely slow performance since upgrade:
The question is, do you also get this with Vivaldi 6.1?
This is something I'd need to test. I do have a faint memory that this issue was introduced in an update, but I'm not completely sure.
And to be honest, when your browser is open a week, it's not weird that it will start to become more sluggish.
I know we expect and just have to deal with this kind of stuff in modern software, but it's still a resource leak that ideally should be fixed. There's no fundamental reason why a browser shouldn't just work indefinitely without a restart.
Also, when you close Viv 6.5 after a week, will it hang in memory? You can check this with a tool like Process Explorer.
Yes. This is most apparent when restarting the browser for a version upgrade, because the browser will close but won't restart. But if I just wait some time โ maybe up to 10 minutes โ the old process will disappear in task manager and the browser will restart. I assume this delay occurs because it's cleaning up the leaked resources. We just need to figure out where the leak is.
-
@ntoskrnl said in Extremely slow performance since upgrade:
@Ayespy I understand where you're coming from, but in my opinion it's worth understanding what we're dealing with to narrow down what we need to test. For example, we know that enabling 3rd party cookies is not going to fix this, so it's unnecessary to test that. We wouldn't learn anything from such a test.
That's what I've been trying to explain. They wanted me to remove all third party security tools, while disabling them has the exact same effect, at least in my case. I do believe the troubleshoot page from Vivaldi is pretty good, it should fix most problems that users may experience. But I believe this particular problem isn't fixable by the user, based on everything I've read so far. Hopefully Viv 6.6 will bring improvement.
-
@ntoskrnl said in Extremely slow performance since upgrade:
@RasheedHolland said in Extremely slow performance since upgrade:
The question is, do you also get this with Vivaldi 6.1?
This is something I'd need to test. I do have a faint memory that this issue was introduced in an update, but I'm not completely sure.
The reason I asked, is because most users reported that they saw this problem after upgrading from Viv 6.1 to newer versions. When they return to Viv 6.1, all problems are gone. That should be the biggest hint to developers.
And Viv 6.2 was a major upgrade that was meant to reduce memory and CPU usage. Instead, some users are seeing the exact opposite, which is weird to say the least, especially because we are all using different hardware. Some have already performed certain tests, like disabling extensions, disabling third party security tools (and Windows Defender), reinstalled Vivaldi and reinstalled Windows. It all makes no difference.
-
@ntoskrnl said in Extremely slow performance since upgrade:
Yes. This is most apparent when restarting the browser for a version upgrade, because the browser will close but won't restart. But if I just wait some time โ maybe up to 10 minutes โ the old process will disappear in task manager and the browser will restart. I assume this delay occurs because it's cleaning up the leaked resources. We just need to figure out where the leak is.
OK I see, perhaps you can perform the same test with Viv 6.1. The reason I asked, is because the ''hanging in memory'' problem started with Viv 6.4 and was still there with 6.5. I didn't know this might be related to some memory leak. I have NEVER seen this problem before, and I have been using Vivaldi since v2. And keep in mind, my security tools are exactly at the same versions, the only thing that keeps changing is Vivaldi, that's another major hint.
-
@ntoskrnl said in Extremely slow performance since upgrade:
I can't be bothered to read 16 pages of posts, but I'd like to add my experience. Vivaldi gets unbearably slow after using it for approximately a week, and it only gets worse from there. It seems to be some kind of a memory/resource leak as it gets worse over time.
BTW, they have just released Viv 6.6, I'm going to test it for a while. Sadly enough it still has a very annoying bug related to the addressbar, so when I'm done testing, I'm going back to Viv 6.1, until they fix the bug. But I wonder if the performance problems have been fixed.
-
Hi,
Please, those still affected even on Vivaldi 6.6, post here
https://forum.vivaldi.net/topic/95634/v-6-6-slow-performance-since-upgradeThank you
-
ZZalex108 locked this topic on