Comment 7 for bug 1110817

I just stumbled on this bug report, and I have no techie input, but I'm here so why not.

We launched Evergreen just about a year ago (2.3.4) and noticed this "leak" problem immediately. Our circ computers were crashing every day. By 4:30 or 5pm, Evergreen was using 1,800,000 K - and that was the breaking point for our computers. Staff learned to either notice the subtle signs of a impending crash... or we'd keep an eye on the clock and just do a reboot when there was a quiet moment (not often during that after-school hour.

Last week we finally upgraded to 2.5.2 and we have not experienced crashes at our circ computers. In fact, it's 4:35pm RIGHT NOW and our two most-used circ computers are running at 650,000 and 860,000 K. These circ computers are running Windows XP SP3.

That's still a lot more than my own computer used for cataloging (Windows 7), which is at 160,700 K.

Maybe this helps, maybe not. But there's definitely a difference in memory use between those versions.