We've got a much newer version of SmartSVN available, [URL="http://smartsvn.com/download"]7.5.4[/URL]. The only reason to stay on 6.6.x variants is if you're using x-merge, are you?
don't i have to pay to upgrade my license to 7.x version ? because we can't pay for an upgrade right now and since we paid for the apps, i think we should have something that doesn't have a memory leak problems.
If you have a current license you can upgrade to 7.5 versions without buying a new license. You can run both versions if you want (but not have two versions open at the same time).
no i can't ! i just test it and it says that my license need to be upgrade and when i use the link to verify if i can have a free upgrade to 7.x version its show me that i need to pay 35$ by license for a total of near 600$ buck. so i ask again, can you create a new bug-fix version for 6.x license?
That means your license has expired (they're valid for a year).
the license did not expired its only that i can not have newest update and that i cannot use email support.
from you buy a licence page :
A permanent license-key for the current version of SmartSVN Professional
One year of free updates (independent of version numbers)
One year of email support
My license are permanent. so, did you mean that the only option for me is to use an older 6.6 version that doesn't have a memory leak problems?
When you buy a license you get the current version of SmartSVN, and can have free updates and support for a period of 1 year.
If your update period has expired you can't update to the latest version without buying a new license.
I'd be interested to see if the issue you're seeing still happened in an earlier version, but ultimately, we will only be fixing serious bugs in 6.6.x variants.
To find out more about the problem:
- What OS are you using?
- How big are the repositories?
- Is the issue reproducible every time you open multiple projects?
- What version of Java are you using?
I replied to this in the "help and support" forum. Upgrading may be a good idea, but it's also quite possibly unhelpful for this situation which may not be a "memory leak" at all. Please see the other post for more.