Hi,
I've had to use the "-J-Xmx508m" argument (after getting an 'out of memory message') to get a query to run that has 700+ results. Is this normal? There won't be many instances where I will have to run this query, but having the Client take 500MB is going to be a tough sell for me for the deployments where I will have to use it. Anything that I can do the reduce it?

Thanks,
Jeff

JIRA v3.11-#288

Jeff,

This is not normal of course, and I can think about two things that could cause out-of-memory on 700-issue download. First, the memory could have been already used up with a large database (like 10,000 issues in the local database, even in the removed connections). Second, some bugs among these 700 could have had a long long long list of comments or a long description with a lot of markup.

We're working to reduce both problems. For the first case, we're redesigning our local storage component right now. For the second problem, we'll replace our XML parsing method and library to save memory and speed up the processing in a future version of JIRA Client.

Currently, the only thing that could be done is, if the problem is caused by the large local db, is to clear the local db and reload queries with those issues that are really needed.

Thanks for letting us know about this problem and sorry for the inconvenience.
Best regards,
Igor

Got this error last night. There should only be 196 items in my db, as that is what is showing in the status bar at the bottom of the screen. The amount of mem the client takes is getting a little out of hand (3x the amount of mem as my local instance of oracle). When will there be a release that will have the redesign?

Also, if I run a query that produces 10 results, then delete the query, does it still cache those 10 results? If so, I'd recommend adding a feature that removes those results if a query is deleted, as it seems that the client will continue to eat mem until there is none left.