From eb951ed07c4830f90eb1f771e36c8f04eb4d0392 Mon Sep 17 00:00:00 2001
From: Ghostkeeper <rubend@tutanota.com>
Date: Mon, 23 May 2016 13:58:36 +0200
Subject: [PATCH] Fix potential concurrency of finishing before connected to
 finishing

This was a concurrency issue: If the slicing was very fast, it could finish slicing before the listener was connected to the message of being finished. Therefore, we should connect to being finished before we even start the start-slice job.

Contributes to issue CURA-1278.
---
 plugins/CuraEngineBackend/CuraEngineBackend.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/plugins/CuraEngineBackend/CuraEngineBackend.py b/plugins/CuraEngineBackend/CuraEngineBackend.py
index a4c7e1c1ed..a854f29bf1 100644
--- a/plugins/CuraEngineBackend/CuraEngineBackend.py
+++ b/plugins/CuraEngineBackend/CuraEngineBackend.py
@@ -155,8 +155,8 @@ class CuraEngineBackend(Backend):
         self.slicingStarted.emit()
 
         job = StartSliceJob.StartSliceJob(self._socket)
-        job.start()
         job.finished.connect(self._onStartSliceCompleted)
+        job.start()
 
     def _terminate(self):
         self._slicing = False