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.
I am testing on a powerful NT machine running build 1113 of FJIE. All IE components are installed. Steps to reproduce: Open about 6 source files in the source editor by double clicking in explorer. Edit a few lines of a couple files. Open a 7th source file. Time the following task: Button 2 click in the source editor to open a context menu for 7th file. I timed this as taking 12 seconds. The second time it is reasonably fast.
12 seconds? I wasn't able to make it delayed more than 1.5s even when trying on just started IDE. My test configuration: NetBeans Build44, Ultra60, 1xUSII@360MHz I've tried FFJIE 1113 too with the same result ( < 1.5s) Maybe it was just a gc() delay? Are you able to reproduce it? Leaving open for your comments.
Before the context menu is displayed it must be checked whether it has sense to provide 'Goto Source' and 'Goto Declaration' in it. Because of this the completion must be used (and initialized if not done so before). However it still shouldn't take so long. To find out the times, please try first to popup completion by Ctrl+SPACE and then right-click to open the context menu. How much the time to open the context menu decreases?
Hi Petr and Miloslav, I have experimented with this some more based on your suggestions. I think this is definitely gc happening and it is showing perhaps two problems. Please note I am running JDK 1.3 on NT 4, sp5. 1. I don't think the default startup mx ms values for java are big enough for ie. 2. It looks like there is an object leak related to context menus in the editor. As I was repeated testing, things got worse and worse. I eventually had to reboot the IDE since it was practically locked up. In my latest testing I had about 20 small files open. This is not atypical for OO systems...I doing real programming work on a small 5K lines application. I do a lot of little changes and then often save my work or compile using context menus. Again I'm running 1113, so this is a bit downlevel. I'll probably upgrade next week and can check things out. Tryed to upgrade this week actually but had some problems with the build I picked up. There is some chance that this could be a hotspot/JDK problem. I would suggest you test on NT if you can. Thanks for your patience with this one. - Steve
Only changed version to Development.
Version: 'Dev' -> 3.2
Haven't seen this since about when Pilsen builds started...stevef 3/26/2001
Target milestone -> 3.2
Resolved for 3.3.x or earlier, no new info since then -> closing.