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 105904 - [heapwalker] References visualization gets broken on Show Nearest GC Root
Summary: [heapwalker] References visualization gets broken on Show Nearest GC Root
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: Jiri Sedlacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-06 16:48 UTC by Alexander Kouznetsov
Modified: 2007-08-15 13:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot (8.33 KB, image/png)
2007-06-06 16:48 UTC, Alexander Kouznetsov
Details
Screenshot (9.23 KB, image/png)
2007-06-06 16:49 UTC, Alexander Kouznetsov
Details
Screenshot (9.28 KB, image/png)
2007-06-06 16:50 UTC, Alexander Kouznetsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-06-06 16:48:06 UTC
NetBeans IDE Dev (Build 200705311200)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251

I have a References window in heapwalker that is more than 8 lines height (some
part of ninth line is visible) and when I perform Show Nearest GC Root that
scrolls to that line the whole view visualization gets broken. See attached
screenshots.
Comment 1 Alexander Kouznetsov 2007-06-06 16:48:47 UTC
Created attachment 43317 [details]
Screenshot
Comment 2 Alexander Kouznetsov 2007-06-06 16:49:22 UTC
Created attachment 43318 [details]
Screenshot
Comment 3 Alexander Kouznetsov 2007-06-06 16:50:47 UTC
Created attachment 43319 [details]
Screenshot
Comment 4 Jiri Sedlacek 2007-08-15 10:43:37 UTC
This could be related to Issue 105882, maybe selecting the found GC root is not correctly called from AWT thread.
Comment 5 Jiri Sedlacek 2007-08-15 13:45:50 UTC
Should be now fixed by fixing Issue 105882. Please reopen if you experience the problem again.

Fixed for Beta1.