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 113982 - [heapwalker] Cancel unneeded computation of fields / references
Summary: [heapwalker] Cancel unneeded computation of fields / references
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jiri Sedlacek
Depends on:
Blocks: 206105
  Show dependency tree
Reported: 2007-08-28 12:11 UTC by Maksim Khramov
Modified: 2012-05-21 08:14 UTC (History)
2 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Maksim Khramov 2007-08-28 12:11:47 UTC
Product Version: NetBeans IDE Dev (Build 200708270000) 
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

Steps to reproduce:
Open any heapdump file. (I use an Netbeans heapdump and it has about 290000 instances of String).
Select java.lang.String class in classes view and open it in Instances view.
Select first instance in Instances pane using mouse.
- Update of Fields and References panes takes about 2 seconds.
Scroll through instances with keyboard (for example from 1 to 30 instance).
- Update of Fields and References panes takes more than a minute.
Comment 1 Tomas Hurka 2007-08-28 12:46:21 UTC
This happens only when you scroll through instances with keyboard. Lowering priority to P3.
Comment 2 Jiri Sedlacek 2007-10-01 10:20:43 UTC
I would say this is not scrolling but sequential selecting. There is an easy workaround for scrolling - use the
scrollbar. When explicitly selecting an instance, I would expect that you want to see the details for it.

Anyway, a fix will be implemented that cancels resolving fields/references when another instance is selected. Not for 6.0.
Comment 3 Jiri Sedlacek 2008-08-25 11:37:56 UTC
Seems to be fixed by faster computing the references - see Issue 139744. Changing to ENHANCEMENT as canceling unneeded
computations is still a valid improvement. 
Comment 4 Tomas Hurka 2009-04-08 12:54:57 UTC
Milestone cleanup: future->next