Comment 14 for bug 1777698

We continue to experience this issue on 3.1.11 (Chrome, and I'm using a Honeywell MS3780 scanner), in the production environment.

I am using sequential barcodes in these tests, since these seem most likely to cause the error to occur (eg ###420, ###421, ###422).

However, I ran the same tests I described in #7 (above) on a stock 3.1 server with the Concerto data and was unable to reproduce the error. I tested the 114 barcode set 3 times and a 40 barcode set once (in different sessions).