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 157848 - Blank debug information
Summary: Blank debug information
Status: CLOSED DUPLICATE of bug 157300
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-03 14:49 UTC by amotz
Modified: 2010-04-29 09:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description amotz 2009-02-03 14:49:08 UTC
On at least the following debug windows: "Local variables", "Watches" and "Breakpoints", only the first column, "Name"
shows anything. All other columns appear blank. The information, however, is there, as tooltips appear, and clicking on
button positions from memory also works.

Sometimes, as a debug window is opened, something flickers in the blank areas, but too fast even to recognize it.

This happens on 2 of my 3 systems, On the high end Linux (Quad CPU, 8GB RAM, 2560x1600 30" screen) and on the Windows XP
laptop with 1680x1050 15.4" screen. On the EeePC netbook Linux, with a 1024x600 screen (The slowest of the three),
everything is OK.

All machines are running Netbeans 6.5 patch 2 (but it also happened in patch 1) and the latest Java, 6u12.

This behaviour is invariant on any one machine.

This problem did not occur in the past, and I only started noticing it after I've upgraded to the 30" screen and a new
graphics card to match. I don't usually debug on the XP, and I only saw the problem after deliberately checking when
writing up this issue.

I suspect some sort of race condition, especially when the flickering effect is kept in mind, as well as the fact that
it happens on the faster computers.
Comment 1 Martin Entlicher 2009-02-03 15:17:48 UTC
I guess we'll have a lot of reports like this.

Please use an older JDK!


*** This issue has been marked as a duplicate of 157300 ***
Comment 2 Martin Entlicher 2009-02-03 15:23:04 UTC
JDK 6u11 should work fine AFAIK.
Comment 3 Quality Engineering 2010-04-29 09:47:18 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.