diff options
author | Alexandru Croitor <alexandru.croitor@theqtcompany.com> | 2016-01-28 15:33:25 +0100 |
---|---|---|
committer | Jani Heikkinen <jani.heikkinen@theqtcompany.com> | 2016-02-04 12:58:06 +0000 |
commit | 32929885f44bb9621ac8cfa2b5c592b0977a123f (patch) | |
tree | 9102f9e61d299f9d5fdd1fafddc26b6030b736a8 /tools/scripts/windeploy-examples.py | |
parent | 46b561970579c08af6e2b2df0713f84396e0da0d (diff) | |
download | qtwebengine-32929885f44bb9621ac8cfa2b5c592b0977a123f.tar.gz |
OS X: Fix crash when setting a custom default QSurfaceFormat.
Setting a new default QSurfaceFormat after
QtWebEngineCore::initialize() is called, might lead to a crash.
This happens when the new surface format has a different OpenGL profile,
compared to the profile created by web engine in the
RenderWidgetHostViewQtDelegateWidget constructor. The default
constructed QSurfaceFormat has an OpenGL Compatibility profile.
Inside the Cocoa platform plugin when a new shared OpenGL context is
created, it fails to initialize the new context because of the
difference in profiles, and thus ultimately creates an unshared
context, which leads to a crash.
Fix consists in using the shared context QSurfaceFormat in the
RenderWidgetHostViewQtDelegateWidget constructor, and also printing
a fatal warning to notify the developer only to set the new
QSurfaceFormat before the application instance is declared.
Bottom line, if the QSurfaceFormat OpenGL profile has to be
changed, it should be done before QtWebEngineCore::initialize() is
called. Doing so after initialize() is called, will lead to a crash.
Change-Id: I8a07211b592143d736b001556b944d4759802396
Task-number: QTBUG-50665
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
Reviewed-by: Michal Klocek <michal.klocek@theqtcompany.com>
Diffstat (limited to 'tools/scripts/windeploy-examples.py')
0 files changed, 0 insertions, 0 deletions