@pichlo has been doing lots of driving with the hope that we can fix the shutdown bug. So far, no luck. But there are things we learned about Pure Maps.

The debug version had each Python call wrapped, so we could see entry and exit of each call to ensure that all calls returned. There were messages added to several Component.onDestruction signal handlers to see whether destructors are called.

@pichlo got some runs that were fine, some hanged on exit. This did not depend on whether voice prompts were used - same behavior was observed in the presence and absence of voice. Outcome of the tests:

* In all runs, successful or hanging exit, python calls always returned.

* In unsuccessful runs, no destructors were called

While not, many destructors were marked by printouts and it looks like, for some reason, closing the app did not start destructors.

Has anyone observed something like it? I am going to summarize it at sailfish-devel list as well.

Would like to thank @pichlo for the work!