This is a known problem with servers that have a lot (tens of thousands) of events; 2GB of memory usage is a pretty extreme case. You may want to clear our your database and start from a clean one - with that many events, it's hard to find anything at all.

The good news is that this will be fixed, hopefully along with much-improved event browsing, in beta8 of the client. The relevant bug is http://improve.bluecherrydvr.com/issues/628.

Right; it is not fixed in the current version of the client, but will be for the next client release. Sorry for the delay; I've been dealing with some high-priority server issues lately, so I haven't been able to work on the client. I'm hoping to update the client to fix some major issues, including this one, at some point this month, and eventually there will be a larger update for events that will change the whole experience.

I added http://improve.bluecherrydvr.com/issues/1015 as a workaround for the imminent beta9 release, so things will at least function until we're able to update the client. Thanks for your patience.

After we release the server beta9 this week, you'll be able to see only the most recent 15,000 events matching your search in the client, which is small enough to not require much memory and to load quickly. The next client release will still contain a more proper fix.

I'm sorry it took so long for that to be dealt with; I should've done this part back in September. There's a lot to do, and things fall through the cracks sometimes. Thanks again for being patient with the beta.