-
Notifications
You must be signed in to change notification settings - Fork 347
Qupzilla consumes insane amount of memory when searching on duckduckgo #1605
Comments
Memory leaking in qtwebkit, probably. |
I have started with a new profile and "managed" (I didn't really want it :-\ ) to reproduce this. So should I make an upstream bugreport now? |
Before filing a qt-bugreport I suggest, that you upgrade your at to 5.4.0 first (if possible). This is the latest release and for example QupZilla issue #1596 is fixed here. If your issue still persists you should try to reproduce it with QtTestBrowser, which can be found on our bug-reports wiki-page (5). |
I've heard that webkit takes forever to compile, so I won't do that right now. However, I have flagged qt5-webkit out-of-date on the Arch Linux packages page (EDIT: whoops, I should have checked on the official sites - it wasn't outdated), so hopefully they'll build it soon and I can test it then and report back if it is fixed. Also I've tried downgrading qt5-webkit to |
Huh? Qt 5.4.2 isn't released upstream yet - not even 5.4.1 is! ;) |
@The-Compiler It was a typo, should be 5.4.0 ofcourse :) |
@JHooverman You have Qt git snapshots, that's other story :) But 5.4.0 is latest officialy released version. |
I couldn't even compile the testbrowser (putting the source for that on github would be nice btw): Also I couldn't really find a qt5-webkit based browser in Arch (didn't try the AUR though), so I've made the upstream bugreport: |
I just found out that it only crashes when I set the useragent to this: I've added an exception for duckduckgo.com to use the "real" useragent string, and now it really doesn't crash anymore: |
I've noticed this too and am able to reproduce. Make it crash super fast by:
Not sure about the useragent being an issue, I set mine to chrome as well since it improves compatibility on some websites. The memory leak is insane, 6GB for me. Locked the whole system up until it got killed by the kernel. Here is the output from dmesg: And valgrind (a memory leak finding tool): There's quite a few memory leaks, I would say it's a major issue. Some are going to be upstream in WebQT. |
Solved in Qt-5.4.2 |
Hello Qupzilla devs,
on two computers running Arch Linux, Qupzilla consumes LOTS of memory when doing a simple search on duckduckgo. For example on my Laptop, the ram usage is about ~200MB with qupzilla open and some tabs. Then I do the search and it goes up to 3GB (!) I've even had to reboot both machines because of that.
I could not reproduce this with a fresh profile. So should I just use a new one?
Versions:
Qupzilla: 1.8.6
WebKit-Version: 538.1
qt5-webkit: 5.4.0-3
The text was updated successfully, but these errors were encountered: