commit 207b4c76881a996f4bbc150fcc678a8a4b426637
author Karsten Thoms <karsten.thoms@itemis.de> Mon Sep 23 23:24:09 2019 +0200
committer Andrey Loskutov <loskutov@gmx.de> Wed Sep 25 05:22:26 2019 -0400
tree ff3d55733fd76207900828e188b150e597f9cbc8
parent 9837a19299bbacfd6520090c3f01742028851517

Bug 551362 - Use FussyProgressMonitor to check usage of monitor

Each resource operation has to fully use up a given monitor. Instead of
creating FussyProgressMonitor instances with getMonitor() and don't
check it further, each operation that takes a monitor gets a fresh or
reseted instance of FussyProgressMonitor, which is checked to be used
up after the invocation. For exceptional cases it sanityCheck() is used
in the catch clause.


Change-Id: Id24576781147be2f07db987ab5fef3b3c9416b7d
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
Signed-off-by: Andrey Loskutov <loskutov@gmx.de>