web page loads very slowly at the beginning in the case of QWebEngineViews in different processes sharing the same cache path
-
wrote on 25 Aug 2023, 06:10 last edited by
For example, application A has a webengineview to load web page, so we start a process a of application A , and then
process a starts a process b of application A . Since they have the same cache path of qwebengineprofile by settingQWebEngineProfile::defaultProfile()->setCachePath(path);
QWebEngineProfile::defaultProfile()->setPersistentStoragePath(path);
, process b shows a white and blank webengineview in a long time before web page finish loading. Is there a solution to fix this?Qt version: 5.15.2
Platform: windows -
-
For example, application A has a webengineview to load web page, so we start a process a of application A , and then
process a starts a process b of application A . Since they have the same cache path of qwebengineprofile by settingQWebEngineProfile::defaultProfile()->setCachePath(path);
QWebEngineProfile::defaultProfile()->setPersistentStoragePath(path);
, process b shows a white and blank webengineview in a long time before web page finish loading. Is there a solution to fix this?Qt version: 5.15.2
Platform: windowswrote on 5 Sept 2023, 12:51 last edited by@gaojinhsu Do you get the same result in release mode ?
-
wrote on 6 Sept 2023, 23:54 last edited by
I don't have any problem loading pages at all. If you have a slow PC and don't want both running at the same time you'll just have to pause the second one until the first one is done.
Or maybe try setting a different cache path for each different URL?
Try pausing the second for a set time , or not starting the second until the first is set and or done.
-
@gaojinhsu Do you get the same result in release mode ?
wrote on 15 Sept 2023, 10:46 last edited by gaojinhsu@ObiWanKennedy yes, I do.
-
I don't have any problem loading pages at all. If you have a slow PC and don't want both running at the same time you'll just have to pause the second one until the first one is done.
Or maybe try setting a different cache path for each different URL?
Try pausing the second for a set time , or not starting the second until the first is set and or done.