From 4a48b6c20ce973660df60104b633dc2ee36bb91a Mon Sep 17 00:00:00 2001
From: hsc <hsc@8c4709b5-6ec9-48aa-a5cd-a96041d1645a>
Date: Sat, 27 Oct 2012 23:18:27 +0000
Subject: [PATCH] nanojpeg: deleting result sets after handling them is not
 racy

Deleting result sets after retrieving them from the "done" queue is /not/
racy.  This obviously was a misinterpretation of crashes with other
campaigns.

git-svn-id: https://www4.informatik.uni-erlangen.de/i4svn/danceos/trunk/devel/fail@1861 8c4709b5-6ec9-48aa-a5cd-a96041d1645a
---
 src/experiments/nanojpeg/campaign.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/experiments/nanojpeg/campaign.cc b/src/experiments/nanojpeg/campaign.cc
index 7b8e21e3..04e4a08e 100644
--- a/src/experiments/nanojpeg/campaign.cc
+++ b/src/experiments/nanojpeg/campaign.cc
@@ -300,7 +300,7 @@ bool NanoJPEGCampaign::run()
 			res->msg.timeout(), res->msg.injection_ip(),
 			bitmask, prev_singleres->resulttype(), prev_singleres->latest_ip(),
 			prev_singleres->psnr(), prev_singleres->details().c_str());
-		//delete res;	// currently racy if jobs are reassigned
+		delete res;
 	}
 
 	finalize_results();