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 250861

Summary: Running "Debug Focused Test Method" takes 24 sec - org.netbeans.modules.maven.queries.RepositoryForBinaryQueryImpl$SrcResult.getRoots() is too slow
Product: projects Reporter: NukemBy
Component: MavenAssignee: Tomas Stupka <tstupka>
Status: RESOLVED DUPLICATE    
Severity: normal CC: markiewb
Priority: P3    
Version: 8.1   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:
Attachments: 25secs of self profiler
Screenshot of sampling - org.netbeans.modules.maven.queries.RepositoryForBinaryQueryImpl$SrcResult.getRoots() is too slow

Description NukemBy 2015-03-03 11:15:09 UTC 
Created attachment 152354 [details]
25secs of self profiler

Steps to reproduce

1. Take test project from here
   https://netbeans.org/bugzilla/show_bug.cgi?id=250833

2. Open any unit test - for example ConvertersTest (org.apache.wicket.util.convert.converters),

3. Right-click within any unit test method - for example thousandSeperator -> select "Debug Focused Test Method"

4. Wait for successful completion

In my NB (Dev Build 201503020001) that action is being executed for 24 seconds. The test itself actually completes in milliseconds. The weird thing is - the green "Continue" button on toolbar becomes active in around 1-2 seconds after test is started and if I press it - test finishes successfully immediately, but ... if i do not press it NB is doing something with significant CPU load for around 22 seconds. 

Self-profiler is attached.

Note: Execution of the test 'without debug' completes in 1.8 seconds.
Comment 1 markiewb 2015-03-03 16:42:47 UTC 
Created attachment 152376 [details]
Screenshot of sampling - org.netbeans.modules.maven.queries.RepositoryForBinaryQueryImpl$SrcResult.getRoots() is too slow

See screenshot - org.netbeans.modules.maven.queries.RepositoryForBinaryQueryImpl$SrcResult.getRoots() is too slow
Comment 2 Tomas Stupka 2015-04-23 09:36:42 UTC 
perhaps fixed in scope of issue #251990
feel free to reopen if this shouldn't be the case

*** This bug has been marked as a duplicate of bug 251990 ***