Avoid crashing if the executing object is already gone when we go into

the continuation.

This happens if Kube is used to look at a folder that is currently being
freshly synchronized, so we continuously get new results.

1 files changed, 3 insertions, 2 deletions

diff --git a/common/queryrunner.h b/common/queryrunner.h
index 155528e..439a990 100644
--- a/common/queryrunner.h
+++ b/common/queryrunner.h
@@ -74,8 +74,8 @@ private:
  * A QueryRunner runs a query and updates the corresponding result set.
  *
  * The lifetime of the QueryRunner is defined by the resut set (otherwise it's doing useless work),
- * and by how long a result set must be updated. If the query is one off the runner dies after the execution,
- * otherwise it lives on the react to changes and updates the corresponding result set.
+ * and by how long a result set must be updated. If the query is a one off, the runner dies after the execution,
+ * otherwise it lives on to react to changes, and updates the corresponding result set.
  *
  * QueryRunner has to keep ResourceAccess alive in order to keep getting updates.
  */
@@ -101,4 +101,5 @@ private:
     ResultTransformation mResultTransformation;
     QHash<QByteArray, qint64> mOffset;
     int mBatchSize;
+    QObject guard;
 };