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.
Product Version: NetBeans IDE 6.7 (Build 200906212001) Java: 1.6.0_13; Java HotSpot(TM) Client VM 11.3-b02 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) -start the ide (not with the clean userdir) -open/create anagram game project -insert porfiling point into anagrams.java, into the method 'nextTrialActionPerformed' profiling point: take snapshot, check 'reset results after taking the snapshot' -insert another profiling point (on the same line) : timed take snapshot, check 'reset results after taking the snapshot' Disable this profiling point -start profiling (memory, record both creation and destruction, record stack traces) -open live results window -select e.g. cahr[] and invoke 'log class history' on it -in the profiled appplication hit the 'new word' button (several times) after random number of tries, the live results window freezes - it does not refresh it`s content, the graph is stopped. Several times pressing the 'new word' button makes it to refresh the content again. Without the disabled 'timed profiling point' it seems to work, although a bit inconsistently: The graph with logged history is shown even after the 'new word' button is clicked several times and then on one click is hidden and disabled.
Seems that this does not affect Product Version: NetBeans IDE 6.7 (Build 200906212001) Java: 1.6.0_14-ea; Java HotSpot(TM) Client VM 14.0-b12 System: Linux version 2.6.28-11-generic running on i386; UTF-8; en_US (nb)
Product Version: NetBeans IDE Dev (Build 091105) Java: 1.6.0_17; Java HotSpot(TM) Client VM 14.3-b01 System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb) I haven't experienced freezing the Live Results window (IDE EDT wasn't blocked). The memory snapshot taken by the profiling point is taken synchronously, if you click the New Word button several times it can take some time to process all the events. During that time no live memory results are sent to the profiler GUI which could cause not refreshing the Live Results window for a while. After all the snapshots have been taken Live Results start to update again.
Reproduced when displaying class history and taken snapshot using a profiling point. Caused by the exception described in Issue 168544 which is now fixed.