summaryrefslogtreecommitdiffstats
path: root/src/core/web_engine_context.h
diff options
context:
space:
mode:
authorMichal Klocek <michal.klocek@qt.io>2021-02-15 08:40:24 +0100
committerMichal Klocek <michal.klocek@qt.io>2021-02-16 23:56:46 +0100
commit827cbb1ff490b6b2da3bf71c6adac0956a6c3261 (patch)
treeb19bb28a55c1a8b4185938880456d3d43e9fd576 /src/core/web_engine_context.h
parent1a2db07cac97db7c3609cf223e807fa62e178a9f (diff)
Fix crashes on BrowserContext destruction
When destroying WebEngineProile we send notifications like content::BrowserContext::NotifyWillBeDestroyed, this works well with global profile where there is no more render process around, moreover we still pump ui messages before we destroy profile. However, with user profiles we destruct BorwserContext and there can be still RenderProcessHost using it. Flush messages before running BrowserContext destructor. Change-Id: I4d8cda2bc1e2ae3dc0781bf3570a36db7d07223a Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Diffstat (limited to 'src/core/web_engine_context.h')
-rw-r--r--src/core/web_engine_context.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/core/web_engine_context.h b/src/core/web_engine_context.h
index a74b83eae..f60082059 100644
--- a/src/core/web_engine_context.h
+++ b/src/core/web_engine_context.h
@@ -108,6 +108,7 @@ public:
static WebEngineContext *current();
static void destroyContextPostRoutine();
static ProxyAuthentication qProxyNetworkAuthentication(QString host, int port);
+ static void flushMessages();
ProfileAdapter *createDefaultProfileAdapter();
ProfileAdapter *defaultProfileAdapter();