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 177974 - CPU at close to 100% for minutes
Summary: CPU at close to 100% for minutes
Status: RESOLVED DUPLICATE of bug 172482
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: PC Other
: P2 normal (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-02 01:37 UTC by bht
Modified: 2010-02-05 03:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread dump (30.99 KB, text/plain)
2009-12-02 01:37 UTC, bht
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bht 2009-12-02 01:37:24 UTC
Created attachment 91975 [details]
Thread dump

This is a bit of a mix of things. NetBeans 6.8 Beta still, haven't installed RC1 yet. I am sorry this is not my style, I would usually want to write a test case.

I downloaded a maven project http://wicketstuff.org/confluence/display/STUFFWIKI/wicket-phonebook which appears to cause problems.

I am not a maven user, but I thought NetBeans will get me started. Finally I thought Maven had downloaded all dependencies but now in the status bar I get "Transfering Repository Index :Central Repository", and the progress bar sitting at 1% for minutes, NetBeans CPU usage is at near 100% all the time, and in the editor I have a dependency graph without knowing what opened it.

In my notes I found there was an option Tools->Options->Miscellaneous->Maven->Work Offline but I can't find this in the current version.

I would think that as an experienced Maven NetBeans user one would not encounter all these issues as I do at once, but on the other hand I thought I should report this because Netbeans is just such a good tool to learn technologies and the NetBeans developers might be interested in this case.
Comment 1 Milos Kleint 2009-12-03 23:22:32 UTC
there is nothing really suspicious in the stacktraces. The download of central repository was triggered by one of your actions. We used to download it on first start, but it was considered bad for "performance" of first startup. So now it's random when it happens. it does take time as it's downloading stuff form an overloaded server. The CPU usage spike is probably caused by other stuff (click on the progress bar to see all current long running tasks). I'd say classpath scanning could be involved.

The options offline switch is now to be entered as "--offline" value into the Global Execution Options field. It will only influence the maven builds though.

The dependency graph had to be started by some of your actions. It's on project popup so you might have accidentally triggered it when things were slow for you.

The problem description is too generic, please include more details with regard to the problem you've encountered. Thank you.
Comment 2 bht 2009-12-04 15:12:22 UTC
My apologies for re-opening this. I am unsure about how to go forward.

I have sumitted an automatic error report that was appended to http://netbeans.org/bugzilla/show_bug.cgi?id=172482

30 seconds delay before the context menu of this maven project pops up. No other tasks running.

I can reproduce this at any time. 30 seconds, 47 seconds and so on. I can comfortably open the task manager and watch the CPU being idle. Then I switch back to NetBeans, which is a blue screen only until the time (30s etc.) is up.

I have been using NetBeans for almost 10 years, have never had a problem like this. I am using it all day every day. But as I wrote, I have not been using Maven with NetBeans. This is probably the key to solving bug 172482 because I can reproduce this so easily, I can see that people are struggling with it and I would suggest to give this a high priority.
Comment 3 Milos Kleint 2010-02-05 03:18:44 UTC
lets close this one and resolve it as part of issue #172482.

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