QtWebEngine extremely slow (windows 7 VS2013 build)

rubizm

I think this issues has something to do with Windows (7) system objects getting hung. It might also be the JetStorm WebStorm IDE which sometimes gets the browsers stuck..

It does recur however..

trallallero

Some problem on Windows 8.
On Chrome the same xhtml file is shown smooth and immediate but on a Qt webengine browser extremely slow.

vinnitu

I have the same situation on window7 32
window Qt 5.4.1 app with embedded QWebEngine.

May be troubles with some of plugins/iconengine/etc?

btw, I use windeployqt.exe

trallallero

Sorry, I forgot to share:

the problem (in my case) was that QtWebEngineProcess was compiled in debug mode only so it loaded all the debug libraries, thus very slow.
I solved (thanks also to Qt support that opened a bug ticket after my support request) executing "jom release" in the directory "qtwebengine/src/process".
A release version of QtWebEngineProcess.exe will be created in the directory "qtbase/libexec"

Hope it helps.

vinnitu

As I see QtWebEngineProcess.exe has 11264 bytes, and seems it is release build, no?

trallallero

Yes, mine is 12288 (Windows 8), the debug is around 50k.
So you have another problem, I guess.

vinnitu

I have check programm in 32 an 64 bits, with and without OpenGL - result the same.

On given machine Windows7 Pro 64x QtWebEngine works singnificte slow.
But on other two machines (Win8 64) it works ok. And ubuntu Ok too.

So what kind of problem can be? ((

NiHoTleHot

Exactly same issue for me. I tried on Macx, no problem. I experience this issue only on Win7 32 with and without OpenGL pre-builds...

yubb

@trallallero error deply myapp,i see http://forum.qt.io/topic/52335/qwebengine-deploy-problem-qwebprocess-exe but is not useful;
the qwebengineprocess.exe debug log is
[0326/201052:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
how i solve my problem,thank

janalleman

Your demo is long over now, but try disabling not-connected network devices, as suggested here: https://bugreports.qt.io/browse/QTBUG-44763t
Worked for me when running the FancyBrowser example code