Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow cpu-greedy page scrolling #837

Closed
Yanpas opened this issue Dec 4, 2017 · 12 comments
Closed

Slow cpu-greedy page scrolling #837

Yanpas opened this issue Dec 4, 2017 · 12 comments

Comments

@Yanpas
Copy link

Yanpas commented Dec 4, 2017

I observe it on Windows 10 (x64 msi installer) in almost all doc pages (python3:bytearray e.g.). I drag side scroller and move it up-down quickily, one of cpu cores quickly goes 100%.

Cannot reproduce on Arch/KDE.

See also #723

@trollixx
Copy link
Member

trollixx commented Dec 5, 2017

It's a problem with (Qt) WebKit, as I can reproduce it outside of Zeal. Reported (sort of) upstream.

CC: @annulen

@Yanpas
Copy link
Author

Yanpas commented Dec 5, 2017

Are there any plans to switch to oficially supported QWebEngine (Blink)?

@trollixx
Copy link
Member

trollixx commented Dec 5, 2017

Nope, all the basic support we had for it has been removed.

Yesterday somebody asked me the same questions on Gitter, and here's my answer:

Unfortunately, Qt WE had issues with rendering docsets as well. It also didn't support setting custom CSS (no idea if it does now). Plus it created some temporary files in user's appdata directory, and that didn't play nicely with the portable edition. Also there was no support for traversing DOM, which might be needed for certain features.

I also recall Qt WE having different performance issues on Windows. So, there's no clear winner here.

I believe The Qt Company doesn't have enough resources to maintain Qt WE at a decent level, but it's just my personal opinion.

@trollixx
Copy link
Member

trollixx commented Dec 8, 2017

According to WebKit developers it's a known problem with Python documentation. See https://bugs.webkit.org/show_bug.cgi?id=180577

There's nothing we can do about it, since we do not generate the docset.

@Kapeli Perhaps you can remove JavaScript that drives the side bar, since the side bar is already cut out in the docset.

@Kapeli
Copy link
Contributor

Kapeli commented Dec 8, 2017

I've updated the Python 2 and 3 docsets and they don't include the sidebar.js anymore. Let me know if that improves things.

@trollixx
Copy link
Member

trollixx commented Dec 8, 2017

@Kapeli Scrolls fine for me, thanks!

@Yanpas Please update the docset, and check.

@Yanpas
Copy link
Author

Yanpas commented Dec 9, 2017

I've updated, it's the same. It's not python doc problem or any docset's, almost every docset is very slow: Apache, c++ etc. QWebKit should be profiled on windows, I don't know

@trollixx
Copy link
Member

trollixx commented Jan 9, 2018

@Yanpas Do you observe any improvements with Zeal 0.5.0?

On Windows it bundles a freshly built Qt WebKit.

@Yanpas
Copy link
Author

Yanpas commented Jan 9, 2018

It's definetely better, but still much slower than any browser. May be closed I think, but qwebkit still needs optimizations

@annulen
Copy link

annulen commented Jan 9, 2018

@Yanpas If you provided us profiling results, we could do something about that.

@trollixx
Copy link
Member

trollixx commented Jan 9, 2018

Closing, per above, and as there's nothing to do from Zeal side.

@trollixx trollixx closed this as completed Jan 9, 2018
@lock
Copy link

lock bot commented Sep 16, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

4 participants