@Menion: Hi Menion, today I had one successful track recording closure and one with infinite loop.
And I had a look into the cache directory you mentioned:
- both, the export file was properly stored, and
- the track was put into the database (checked with LMP, while LM4 was in infinite loop)
- and two files stayed in that cache directory: track_0.lb (47 kB) and track_breaks_0.lb (4 B), both with timestamps from my closing the track.
Then I killed LM4 via Android swipe, moved the two files away and restarted. And LM4 still ended up in an infinite loop - AND it created a new track_0.lb (8 B).
Hence the information about a "recording" track must be somewhere else, too, beyond the existence of the file(s) in the cache directory.
Another round of stop, delete cache file and restart made LM4 behave.
What I also observed: when I installed the very latest Beta today and started LM4, the boot sequence paused a bit around 11%, then rushed to 65% or so and soon after LM4 showed the map.
After the hard stop(s), though, the restart CRAWLED from 11 to 24, ...., 65% or so, then as above, taking MUCH longer. There was NO change in map setup inbetween.
So, again, there must be a weird trigger inside LM that makes this difference to the worse.
I hope those observations will help cornering the error ...
Good luck and kind regards
Michael