diff options
| author | Andras Becsi <andras.becsi@digia.com> | 2014-07-08 17:24:07 +0200 |
|---|---|---|
| committer | Andras Becsi <andras.becsi@digia.com> | 2014-07-11 17:10:50 +0300 |
| commit | 82e327e5bc8ff3073f8ca8558dce4066a10f6e4a (patch) | |
| tree | eaa5308830dc49a69936c8665fcb9cb1c3b3e941 /basicsuite/webengine | |
| parent | 980262215341472dbff0967f4e7687ef7a9aa0db (diff) | |
webengine: Add slight delay before loading the start page
This is a workaround that seems to prevent the random start-up
freeze on eAndroid.
The freeze is a deadlock in the graphics stack, specifically
in eglMakeCurrent, related to known GPU driver problems with
context sharing on Android on some devices. Chromium has some
workatounds for these problems, but our snapshot is not recent
enough to have reliable quiks for all configurations we support.
Since the QML Loader element used in qtlauncher and WebGL content
seem to be the only way to sporadically reproduce the freeze
this workaround should be sufficient until we do more testing
with an updated snapshot.
Change-Id: I02ec9f441c06ee3243e9975e4a49217400df27f2
Reviewed-by: Laszlo Agocs <laszlo.agocs@digia.com>
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@digia.com>
Diffstat (limited to 'basicsuite/webengine')
| -rw-r--r-- | basicsuite/webengine/main.qml | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/basicsuite/webengine/main.qml b/basicsuite/webengine/main.qml index c8ea895..d2f5184 100644 --- a/basicsuite/webengine/main.qml +++ b/basicsuite/webengine/main.qml @@ -56,7 +56,7 @@ Rectangle { width: 1280 height: 800 - property url defaultUrl: Qt.resolvedUrl("content/index.html") + property url defaultUrl: Qt.resolvedUrl("about:blank") function load(url) { mainWebView.url = url } ErrorPage { @@ -92,6 +92,13 @@ Rectangle { errorPage.mainMessage = "Protocol error" } onActiveFocusChanged: activeFocus ? hideTimer.running = true : toolBar.state = "address" + + Timer { + interval: 1500 + running: false + onTriggered: defaultUrl = Qt.resolvedUrl("content/index.html") + Component.onCompleted: start() + } } MultiPointTouchArea { |