Closed pLeminoq closed 5 years ago
The exception was likely caused by a timeout when restoring a snapshot. A reason why this could have happened is that the transaction id of a unit has been split by service type and service updates can overwrite each other. E.g. an update for a color state overwrites the current brightness value removing the available transaction id. Therefore the UnitSynchronizationFuture would not return resulting in a timeout. This should be fixed by commit f0e3e5752ccfb4073e01e8692b0fb44155513993.
The second issue that the method returns too soon has also been improved but I think it can only be guaranteed by fixing issue #89
Issue is outdated and causing issues are fixed.
In the hope of finding information on issue #73 I repeatedly changed the standby state of the home location in my system. This did not help find anything regarding the memory leak bug revealed two other things:
After finding out that the method returns to soon I changed the test to switch the standby state every minute. After running for a while the exception mentioned above occurred again so the state could not be switched anymore. This also did not result in an out of memory error.