737 B
737 B
comment:1 Changed 3 years ago by zzz
Status:new → open
Can't figured out why it blocked there, unless just bad luck.
We could pull the logging out of the lock, but, notifyMassive is about to soft-restart the whole router, so the wait is just beginning.
This is a side-effect of our clock management scheme, where we don't have a separate thread doing the slewing and shift detection (that would be a lot harder). So anybody could get stuck in now(), but it hardly ever happens.
We did confirm that the log LBQ is 1024, so it's almost impossible that it filled up, especially on Android with default settings.