Please consider to instead vote for: https://smartgit.userecho.com/topics/655

But you are requesting this feature for SmartGit's Git integration, not its Mercurial integration?

Thanks, I see now.

The link points to /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}/comments/{commentId} which is about pull request comments only. SmartGit is already using this API. AFAIU, there is currently no API for ordinary commit comments.

Please have a look at following How-To which explains using JVisualVM to profile SmartGit:

http://www.syntevo.com/doc/display/SG/Inspecting+SmartGit%27s+process+using+JVisualVM

In a first step it would be important to understand whether Used heap size properly decreases when closing a Log or a repository or whether there might actually be some kind of memory leak. It would also be interesting whether you can get the overall (reserved) Size to decrease when invoking Perform GC from within JVisualVM.

Did you check the allocated memory in some operating system tool (like the Windows task manager) or in a Java profiler, like jvisualvm? I'm asking because after closing a Log window or closing a repository *and* invoking the garbage collector, the heap size should definitely go down (I've just verified both). This still does not mean that the garbage collector will actually release physical memory back to the system. The behavior of the garbage collector depends on the operation system, too. Thus, more details, including VM telemetries like the one produced by jvisualvm would be helpful.

Sorry, not sure what happened to my reply: I can reproduce the slowness and there are some promising ideas to make .gitignore processing faster which we are investigating.

Version 17.1 comes with an optional compact display: Changes|Compact Change Display

This "building" thing is what frightens me, as I guess it will require an appropriate build environment. But: you could send a complete directory listing (dir /b /s) and let me know the exact SHA of your HEAD. Then I'll be able to reproduce your state.

Can you please provide an entire repository, including working tree and ignored files to reproduce the problem? I guess a DropBox upload will be helpful.