@tthomas48 said:
...
After a while we started noticing that around the same time of night the queuing system would go completely out of control.
...
i am a bit off-topic, but this one reminds me of a bug i encountered
after updating one of our application to use the system clock instead
of the encoder signal linked to a conveyor belt: the software, though
working without any problems all day long, would crash on every
overnight test.
it took me some nights to be able to reproduce the problem at
will: if a (simulated) product entered the system the second before
midnight, the software would wait for an event to happen just after
midnight, but the system clock was reset to 0 at midnight, so the event
would never be fired and products would continue to stack up into the
system until the event queue overflows.
i remember i even considered staying all night long starring at the
computer just to see the software crash... bad bug ! bad, bad bug !
sit, bug ( (c)2006 ParkinT )
(fyi: the same problem existed before the update. when the encoder
would wraparound, it would make the software crash. the problem was
known, but the original developper calculated that
it would take some months before it could happen, and so decided to
NOT correct it... and NOT document it !)