The Auction application clocks are working okay when starting and loading the application in MsEdge, however after a few hours (4.5 hours) they are slow, ticking once every few seconds.

Testing results:
The browser memory tests have been run with auction on MsEdge38, FF51, Chrome56 on the Windows10 test machine.

On MsEdge, after leaving the auction application open in 2 tabs for ~16 hours (session timeout of the app was increased so that session would not expire), both tabs were found with the clocks ticking once every ~20 to 50 seconds. When mousing over, or clicking on the page, the mouse pointer showed a 10-20 seconds busy state, however no errors were found.
Start time memory:
18860
38740
End time memory:
10936
59184

The test was repeated on MsEdge on my Windows10 PC, and a similar result was found; after 4.5 hours, clocks were ticking in first tab; in second tab, clocks ticked once every 3-4 seconds. After opening the browser console, or when changing tabs, the browser window becomes non-responsive, however no errors.
Start time memory:
20396
42020
End time memory:
28864
332764
108
44148


The Browser Memory Test was repeated on MsEdge/Window10 with ICEfaces 4.1.1 release libraries. The results are almost the same, no server or JS errors have been seen:
" Clocks tick randomly, every 10-20 seconds in both tabs.
  When changing tabs, or when clicking on the demo page, the browser window is very slow, the mouse pointer showing a busy state for 3-10 seconds, however no errors. The browser console cannot be opened, its content is grey/blurred."
Start time memory:
19996
38952
End time memory:
17360
72908