When editing a java class if the user right clicks on a JPA pojo java class definition and chooses "Navigate|Go to Source" it works fine the first time.  When you return back to the original class and highlight the same JPA pojo java class definition and right click on it the IDE hangs for over a minute before popping up the dialog.   The IDEs memory usage also spikes up very high.  If you do it 3 or 4 times the IDE hangs eats up all available JVM memory and has to be killed manually. 

PersonJpaBean personInstance = null;   

  Highlight "PersonJpaBean" right click select "navigate| Go to Source" go back to original class and do it again the IDE hangs.

Using Oracle JDK 1.6.0_34 32bit on Windows 7 64bit.  This works fine in Netbeans 7.1.

Milo please evaluate..

This looks like a duplicate of bug 216053
Could you please try a later dev build?

It seems JPA-specific. Sergey, is it duplicate of Bug #216053 as bht suggesting?

can't say, not so much details, 
 rkite can you try latest dev build? and reopen the issue if it's reproducible and please provide snapshot in this case.

*** This bug has been marked as a duplicate of bug 216053 ***

(In reply to comment #5)
> can't say, not so much details, 
>  rkite can you try latest dev build? and reopen the issue if it's reproducible
> and please provide snapshot in this case.
> 
> *** This bug has been marked as a duplicate of bug 216053 ***

  I can give it a try.  I have switched back to 7.2.1 which works fine.  


   Others here have seen the runaway memory problem as well.  Our project is large over 1 million lines of code so it is a good test.

  The right click "Navigate|Go to Source" issues appears to be fixed.  


  The memory issue may be as well but it does use more memory than the 7.1.2 release.  The 7.2 release IDE would eventually eat up all of the memory allocated (1024meg) and hang.  My memory settings are -JXms512m -JXmx1024m.   With only 5 classes open in the editor the memory is climbing to over 400 meg but then returns to 314 meg.  This issue maybe fixed as well but I will not know until I push it with some development time.   

Thanks

ok, thanks. nice to have navigation fixed.
memory may be either related to persistence or not, or be a combination of features. when I'm working with nb modules(do not contain persistence support at all I have jumps up to 700mb and back to usual level 300mb and it doesn't mean memory leak in my opinion as usage is restored after jumps. But may it's not good too especially for "5 classes".

(In reply to comment #8)
> ok, thanks. nice to have navigation fixed.
> memory may be either related to persistence or not, or be a combination of
> features. when I'm working with nb modules(do not contain persistence support
> at all I have jumps up to 700mb and back to usual level 300mb and it doesn't
> mean memory leak in my opinion as usage is restored after jumps. But may it's
> not good too especially for "5 classes".

  The memory issue was happening to several of us using 7.2.  It appears to be a different issue.  It would fairly quickly eat up all the memory and then hang. Happened even when only 1 class was open in the editor.

   Looks like the run away memory issue is fixed as well.  

   After a few days of development with a large project NetBeans Build 201208270001 is working well for several developers.  

--Thanks
Rodney