the plugin eats all free memory under Ubuntu 9.10/NetBeans 6.7+

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Just install nbgit as a plugin, open any project and see how it eats all
free memory.

What versions of NbGit, NetBeans and Java are you using?
On what operating system?

- nbgit: 0.3
- Ubuntu 9.10 (64 bit)
- NetBeans (6.7, 6.8rc2)
- Java:
java version "1.6.0_15"
Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02, mixed mode)

Regards,

Konstantin (k.dzreyev@gmail.com)

Original issue reported on code.google.com by k.dzre...@gmail.com on 7 Dec 2009 at 3:37

[GoogleCodeExporter]

I haven't been able to reproduce this. Do you use third-party plugins
other than nbgit?

Original comment by jonas.fonseca on 10 Dec 2009 at 1:42

[GoogleCodeExporter]

Exactly the same problem. Every action like status eats about 200MB of memory. 
So
only a few actions and I'm forced to restart NetBeans. This makes nbgit 
unusable of
course. Exactly same enviroment no third-party plugins. Problems exists with 
nbgit
0.2 too.

Original comment by martin.h...@gmail.com on 2 Feb 2010 at 9:04

[GoogleCodeExporter]

Same problem here, but I just started experiencing it.  I think it was 
triggered by 
the rapidly growing size of the git repository.  At least that's my best guess. 
 The 
problem is reproducible using both the latest 6.9 beta and the 6.8 version I 
normally 
use, using the appropriate nbgit plugins.  

Original comment by evotur...@gmail.com on 25 May 2010 at 2:02

[GoogleCodeExporter]

Yep... My project is also huge but I had no issues on 32 bit Ubuntu: it came 
when I
migrated to Ubuntu 64 bit

Konstantin

Original comment by k.dzre...@gmail.com on 25 May 2010 at 7:27

[GoogleCodeExporter]

It is interesting, I don't have any problems with it when using a smaller 
repository.  
It may not be size, but there is some feature of the repository that is causing 
the 
crazy high memory consumption.  

I'm a bit surprised because I set the JVM startup parameters for NetBeans to 
limit 
the maximum memory that the JVM will use, but it is just ignored.  My guess is 
that 
nbgit actually runs in a separate process.  This probably isn't optimal.  If I 
only 
have 4 gig in my machine, I will still only have four gig in my machine when I 
run 
nbgit.  

Original comment by evotur...@gmail.com on 27 May 2010 at 6:11

[GoogleCodeExporter]

Just thought I should note, I'm using a 64 bit operating system and JVM.

Original comment by evotur...@gmail.com on 30 May 2010 at 3:53