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.
[nb_dev](200405182245),[jdk1.5.0](b51) Steps to reproduce: - run IDE - make 10 copies of attached file to the same package - try to select one by one of copied files in Projects View (select first - CTRL+right click, select second - CTRL+right click, ......) - push Open from popup menu on multiselection -> IDE hangs if you have selected 7 -8 files (attachment 1 [details]) or after trying to open (attachment 2 [details])
Created attachment 14992 [details] Big file for test
Created attachment 14993 [details] attachment 1 [details] - after slelection 7-8 files
Created attachment 14994 [details] attachment 2 [details] - after opening 10 big files
By the way: - it's regression !!!! - it works fine in previous build 200405171800 !!!! - it's reproducible on all platforms WinXP,Win2K,RH9,Sol9 - this test case is very important from performance point of view and it's one of the test cases used for testing performance of our IDE
Excerpt: org.openide.text.DocumentLine$Set.getLines(DocumentLine.java:865) org.netbeans.modules.debugger.projects.ContextProviderImpl.getCurrentLineNumber(ContextProviderImpl.java:131) org.netbeans.modules.debugger.jpda.ui.Context.getCurrentLineNumber(Context.java:106) org.netbeans.modules.debugger.jpda.ui.actions.ToggleBreakpointActionProvider.propertyChange(ToggleBreakpointActionProvider.java:43) The problem is apparently in a call to org.openide.text.DocumentLine$Set.getLines() performed by the debugger. The getLines() method iterates through all the line numbers in the document and requests creation of a Line instance for each of them. This will definitely be very slow for larger documents. To be honest I don't know whether I should pass this to the debugger or openide/editor. The method should not be used or its implementation should be improved if possible. Passing to openide/editor for further evaluation.
Very probably duplicate of Issue #43484.
yes it is a duplicate *** This issue has been marked as a duplicate of 43484 ***
verified duplicate