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.
When editing java code, javadoc will sometimes freeze when viewing class methods and properties. For example, I will enter "jButton1." and wait for javadoc to show the available methods. I will move up and down to see the details for each method. Sometimes javadoc will not display the details for the new method I select, but keeps displaying the details for a previous method. If I keep selecting other methods, it may eventually update the details to reflect the currently selected method, and javadoc may keep working for the next several selections before it once again freezes. Note that I am allowed to select (highlight new methods), but the details don't update to reflect the selection. Sometimes I need to make 15 or more selections to see this behavior. Sometimes it occurs on the third or fourth selection.
Relates to code completion. Reassigning.
Hi, since this normally works fine we would need to know more to track it down. First could you please attach here your log file (eg. <ide-userdir>/var/log/messages.log)? When the javadoc window gets stuck is it stuck forever (if you don't change the selected method) or will it eventually show correct javadoc? Is there anything else running in the IDE (eg. scanning in progress, tasklist, etc)? This may not be of any use, but could you please generate a threaddump at the time when the javadoc window is stuck (http://wiki.netbeans.org/GenerateThreadDump)? Thanks
From reporter by email: First, thank you for looking into this. It drives me crazy! I hope you will tell my configuration is in error. Thanks, mike. Attached are the messages.log, ThreadDump, and a screenshot I took with my camera when javadocs is "frozen". This test was made immediately after opening NetBeans. In a very simple demo program, I entered "jButton1." to see the available methods. Sometimes, it will freeze the first selection I make; other times, it will not freeze until after a dozen or more selections. I was not (conscientiously, at least) doing anything else in NetBeans. I don't know if the ThreadDump will be helpful. To enter the Ctrl-Break in the console window (I was running nb.exe), I first had to switch from the netbeans window to the console window. When I switched, the javadocs window disappeared from netbeans. When javadocs is frozen, it never spontaneously unfreezes. When the bottom half of javadocs screen is frozen (the part that displays the actual documentation), I can still scroll the upper half to other methods or properties. I can even select and highlight them. Eventually, the bottom half will become active and display the desired method. I can record a video of this if you'd like to see it. (To save space, I will convert it to DivX unless told otherwise.)
Created attachment 78641 [details] IDE log file
Created attachment 78642 [details] Threaddump
Created attachment 78643 [details] Screenshot showing the javadoc window stuck on a wrong field
Thanks for the information. There is nothing in the log file and the threaddump (as you mentioned) shows no activity. It was probably captured too late. "Eventually, the bottom half will become active and display the desired method." - So the javadoc window is not stuck forever. It will eventually show the right information. It's just too slow. Correct? Does this happen for every source in your project? And for every project that you work on? Or does it happen only say for JDK classes or some other library classes or only for classes in some of your projects?
This problem occurs for all my sources, all my projects. I only use javadoc for JDK classes. Once frozen, if untouched, the javadoc will not return. For example, per the attached test1_screenshot.jpg, the javadoc has frozen displaying the Item_Changed_Property although I had selected Left_Alignment. javadoc will continue to display the Icon_Changed_Property while I actively change my selection to say Height, Framebits, or Horizontal. Eventually, perhaps, 5 or 6 selections later, I might select Leading and the javadoc will change directly from Icon_Changed_Property to Leading without showing any of the selections I made in between. It is all very random, yet also very certain to occur at some point. I have updated NetBeans a few times. Perhaps, there was a problem in the update process. If helpful, I can delete NetBeans (and possibly the JDK) and do a fresh install.
Ok, thanks. It's strange, because it's working just fine in both 6.5 and dev builds I'm using. Let's see if there are more complaints and clues that would point us in the right direction.
Resolving all issues with milestone "future" as LATER. If you feel strongly that it should be implemented please reopen and set the target milestone to "next".
NetBeans.org Migration: changing resolution from LATER to WONTFIX