chronoKeeper gets an occasional SEGFault that appears to be some race condition
I've seen it happen very infrequently when the chronokeeper was left running after all the stories had been released and the DataStore had been cleared.
I've seen it happen with multiple slow clients sending events and the cronokeeper is being "paused" (ctrl-Z) then resumed
chronoKeeper gets an occasional SEGFault that appears to be some race condition
I've seen it happen very infrequently when the chronokeeper was left running after all the stories had been released and the DataStore had been cleared.
I've seen it happen with multiple slow clients sending events and the cronokeeper is being "paused" (ctrl-Z) then resumed
more investigation is needed