Thanks for the bug report. Would it be possible for you to supply a sample code snippet which is causing the error so that we can reproduce it internally?
Just to check that this is a live issue could you ensure that you are using the latest version of the API (currently 2.2.4) - In order to do this, just ensure the library is loaded with the following:
Without looking at the code (or having the combination of Hardware/software you mentioned at hand) I have a couple of wild guess suggestions which may (or may not) work:
- It may be the case that this is a bug within the canvas rendering, in which case the following switch to DOM Mode may work:
- It may also have been the case that there was some sort of network /infrastructure issue last week when you ran your test. So is it still an issue?