A customer complained of Intermittent Run Input issues. The Controller would appear to intermittently not respond.

The issue was tracked down to a memory leak related to the Bundle Ticket option and deleting orders.

The scenario to reproduce the problem involved a long period of time where orders were deleted immediately after production completion. When this happened, the orders were able to be deleted from the user interface or Eclipse but they are only hidden. The final deletion of the memory was not able to take place due to an invalid Memory Record Id test that failed to consider records that are marked for deletion. Eventually the number of orders and item records needing memory deletion resulted in a statistically significant(noticeable) chance that the run mode would be locked out when the user attempted to enter run.

The invalid Record ID test was fixed.

To prevent small run lockout times from causing random Run Input failures, the run lockout test now allows a 100msec delay. If the lockout is released within 100msec the controller will continue into the run mode, otherwise the run mode will be forced to HALTED (as displayed on the screen).