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.
Build: NetBeans IDE Dev (Build 201510190002) VM: Java HotSpot(TM) 64-Bit Server VM, 25.51-b03, Java(TM) SE Runtime Environment, 1.8.0_51-b16 OS: Windows 7 (report with automatic log from within NB is not possible, due to #256039) create class: public class Triple<T1, T2, T3> { private T1 _value1; private T2 _value2; private T3 _value3; public Triple(final T1 value1, final T2 value2, final T3 value3) { _value1 = value1; _value2 = value2; _value3 = value3; } } - place pointer onto any T1 and press Ctrl+R (Rename) - rename type to String - place pointer onto any T2 and press Ctrl+R (Rename) - rename type to String --> NB responds with a nullpointer exception (reported as #256037) - press Ctrl+S (save) --> NB completely freezes, need to be killed by taskmanager Yesterday, I faced a complete freeze by renaming a css class in a JSF page, which had not been reproducible. This might have been related to this bug Renaming a type reproduces the bug.
If you can reproduce it Michael, can you please generate a full thread dump while the IDE hangs and attach it here? Thanks a lot! I could only reproduce the NPEs, not the freeze itself. Since it is not reproducible, downgrading priority.
Freeze occurs only during save. Maybe only on a windows system. I'm going to try at home (win 8), if I'll get time.
Created attachment 156832 [details] IDE log
Please attach a thread dump[1] from when the IDE is unresponsive. Thanks! [1] - http://wiki.netbeans.org/GenerateThreadDump
Jirka confirmed: "I could only reproduce the NPEs, not the freeze itself. Since it is not reproducible, downgrading priority." He could confirm the cause, not the freeze. Close as "invalid" does NOT solve and existing problem. Reopened. I'm going to try a dump, even there is a freeze.
According to your build datetime 201510190002 this is a dup of issue #255955 very likely. Please download a newer build. If the problem would persist please reopen. Thanks. *** This bug has been marked as a duplicate of bug 255955 ***