Josh, that's very interesting. One of our affected libraries makes heavy use of patron search for retrieving patrons. I found a bug report in Launchpad about patron search using up RAM:

I did a quick test that seemed to confirm the issue; my findings have been added to the bug report. I'll need to do more testing and follow up with our other affected libraries to see if they use patron search regularly.


On 2017-02-01 02:19 PM, Josh Stompro wrote:
I've seen issues with using the patron search vs checkout.  Patron search seems 
to leak memory.  So I've seen issues where staff always go to patron search, 
even if they have a patron barcode, after a while the client will get 

Josh Stompro - LARL IT Director

-----Original Message-----
From: Open-ils-general 
[] On Behalf Of Jeff 
Sent: Wednesday, February 01, 2017 3:43 PM
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 
Jeff Davis
BC Libraries Cooperative

Reply via email to