That's always been it's way of closing... the TTC turning --- and then sitting there for a half a minute, maybe longer on a slow device. I've not looked or paid attention to watch what the CPU counter does in BOINCTasks... whether it stops whilst elapsed continues. Other sciences as e.g. HCC sit there at 99.818% for a little with both the elapsed/cpu continuing.

Given the different underlying science engines, the programmers have to find creative ways to get the BOINC wrapper around the application and this came out on this version. It is really not relevant to the outcome and I'd be very cautious to mess with something not affecting the result in B/C type app that took a long time and multiple beta's to get working reliably.

--//--

edit: As I noted, the B/C type runs on the same app build then watched a SE finish. Between the change of TTC to --- and the upload starting was less than 2 seconds. Did not see elapsed or cpu time move during that < 2 second wrap-up phase.