We are noticing a similar and vexing problem at one of our newly migrated libraries. The staff client slows and throws a series of "Network not found," "String is not a function," and other random errors. We have verified that is not a latency problem caused by insufficient bandwidth. They have plenty. The PCs are new. No other libraries in our consortium are affected. Any insights would be appreciated.
Thank you, Scott Scott Thomas Executive Director PaILS / SPARK (717) 873-9461 scott.tho...@sparkpa.org -----Original Message----- From: Open-ils-general [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jeff Davis Sent: Wednesday, February 01, 2017 4:43 PM To: email@example.com Subject: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client Our consortium has a few libraries where the Evergreen staff client periodically becomes unusably slow or freezes up altogether. I'm curious about other libraries' experiences with this problem. 1. Does the staff client slow down or freeze up regularly at your library? How often does it happen? Are there any noticeable patterns (e.g. are only circ stations affected, not cataloguing)? 2. How do you deal with the problem? We usually recommend limiting the number of open tabs, restarting the client periodically throughout the day, and increasing RAM. 3. If you use the web client, have you noticed an improvement? We suspect that the root of the problem is the ancient version of XULrunner used by the old staff client, but we haven't had the opportunity to compare the web client in production. -- Jeff Davis BC Libraries Cooperative