search

vikashsingh009 / jzebra

Automatically exported from code.google.com/p/jzebra
0 stars 0 forks source link

JavaScript Listener Blocked by Non-Responding Printer #175

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
When printing to a non-responsive printer, the events start queuing up and put 
the applet in a race condition.

This is caused by exploiting a single-thread listener for all web browser 
functions.

The downside of this is 1. Threads never give up, 2. If a programmer would like 
to give a user the option to print to a different printer, the option may never 
become available as the applet tries to communicate with a malfunctioning 
device.

A architectural rewrite of the JavaScript listener is overdue, but needed to 
handle this bug properly.

The symptom of this bug is all buttons in sample.html become non-responsive.

If verbose debugging is turned on, you will see something like this in the 
console:

network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45
network: Created version ID: 1.7.0.45

-Tres

Original issue reported on code.google.com by tres.fin...@gmail.com on 5 Nov 2013 at 3:02