NOTICE: Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by Miroku4444, April 16, 2012, 07:17:27 PM
QuoteI am concerned about a subset of users who saw the original issue in .68 (not this issue), and am therefore engaged in some refactoring to make sure nobody ever sees that older issue again.
Quote from: bitsum.support on April 20, 2012, 11:45:59 AMOk, in v126.96.36.199, the explicit shutdown order was changed so that the GUI will always terminate before the governor. This will fix the issue without any time bias (shutdown take 3 weeks? That's fine).
Quote from: bitsum.support on April 20, 2012, 11:45:59 AMAgain, I do apologize for not doing this first. I had hoped that the receipt of WM_QUERYENDSESSION by the GUI would always pre-empt the receipt of WM_ENDSESSION by the governor, regardless of shutdown order, but was apparently incorrrect in this assumption (which I was concerned about). I was attempting to make as few changes as possible, instead of taking a broader look at the issue.. I suppose.UPDATE: Now issued, all tests have been fine, I'm pretty darn sure this will go good for *every user*.
Quote from: bitsum.support on April 20, 2012, 11:45:59 AMThe original issue, of course, was me backporting the governor recovery mechanism to v188.8.131.52. That was the true mistake here.UPDATE: Now issued, all tests have been fine, I'm pretty darn sure this will go good for *every user*.