summaryrefslogtreecommitdiff
path: root/platform
diff options
context:
space:
mode:
authorMichael Muesch <muesch@fb.com>2019-06-25 13:24:31 -0400
committerThiago Marcos P. Santos <tmpsantos@gmail.com>2019-06-26 17:15:39 +0300
commitabf60753cb4671099053e6ad8a8c90535d66ccdc (patch)
treedd374017ed2b9ad88baff5a8c8176a8f18ede219 /platform
parent3b90d95b938485936e9295c8a4044c93c7939cbf (diff)
downloadqtlocation-mapboxgl-abf60753cb4671099053e6ad8a8c90535d66ccdc.tar.gz
Remove assert from deconstructor of run_loop.cpp
In the deconstructor of run_loop.cpp there is an assert that checks to make sure the Scheduler is null before setting it to null. In some rare scenarios where the app is being put into the background or closed the Scheduler can be null before the deconsturctor is called. This can cause an unnecessary crash. Since the goal here is to just set the Scheduler to null either way, it should not matter what the state of the Scheduler is before the function call.
Diffstat (limited to 'platform')
-rw-r--r--platform/darwin/src/run_loop.cpp1
1 files changed, 0 insertions, 1 deletions
diff --git a/platform/darwin/src/run_loop.cpp b/platform/darwin/src/run_loop.cpp
index 76f469b22f..0e22dc9e33 100644
--- a/platform/darwin/src/run_loop.cpp
+++ b/platform/darwin/src/run_loop.cpp
@@ -25,7 +25,6 @@ RunLoop::RunLoop(Type)
}
RunLoop::~RunLoop() {
- assert(Scheduler::GetCurrent());
Scheduler::SetCurrent(nullptr);
}