This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 192154 - refactoring crashed when renaming method
Summary: refactoring crashed when renaming method
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: Macintosh (x86) Mac OS X
: P2 normal (vote)
Assignee: Antonin Nebuzelsky
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2010-11-19 04:38 UTC by billshannon
Modified: 2011-03-07 22:54 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log when the problem occurred (259.45 KB, application/octet-stream)
2010-11-19 04:38 UTC, billshannon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description billshannon 2010-11-19 04:38:26 UTC
Created attachment 103091 [details]
messages.log when the problem occurred

I'm using NetBeans to develop GlassFish 3.1.

I have a class with a method IsThisHostLocal.  I want to rename it to
isThisHostLocal.  Someone added an isThisHostLocal method that calls
the IsThisHostLocal method.

I deleted the isThisHostLocalMethod.  I then used refactoring to rename
the IsThisHostLocal method.  It failed with a NullPointerException.
See attached messages.log.
Comment 1 Marian Mirilovic 2010-11-19 10:39:59 UTC
Looks like duplicate of issue 192155, it ends up for Out Of Memory. What I am concerned about is that this one is reported against NB 6.9.1 !!!
Comment 2 billshannon 2010-11-19 20:30:45 UTC
The underlying issue may be the same, but the manifestation is quite different.
6.9.1 failed, told me about it, and kept going.

7.0beta had to be killed.
Comment 3 Jesse Glick 2010-11-19 21:08:48 UTC
Indexing seems to have been pathologically slow, e.g.:

INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: file:/Users/shannon/v3/web/web-ajp/src/main/java/ took: 14718 ms (New or modified files: 33, Deleted files: 0) [Adding listeners took: 9 ms]

Seems the IDE was up to the very limits of its heap to begin with. 500Mb is skimpy for working with an enormous set of projects like this.
Comment 4 billshannon 2010-11-19 22:51:43 UTC
I believe I had cranked up the heap to 768MB.  I recently increased it to 1GB.
Comment 5 David Konecny 2010-11-21 20:20:49 UTC
Fixing issue 192155 will most likely resolve this issue as well. Leaving open for now as alternative test case.
Comment 6 Antonin Nebuzelsky 2011-03-07 22:54:13 UTC
Closing fixed with the fix of issue 192155.

Soft-referencing MavenProject instances should allow as much heap as possible when needed for the scanning/refactoring needs. The heap usage is now even more flexible than with 6.9.1.