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 48390 - 100% CPU usage in JavaParserGlue and CompatibleNode
Summary: 100% CPU usage in JavaParserGlue and CompatibleNode
Status: RESOLVED DUPLICATE of bug 48158
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-02 15:57 UTC by _ tboudreau
Modified: 2007-09-26 09:14 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (35.66 KB, text/plain)
2004-09-02 15:58 UTC, _ tboudreau 		Details
More thread dump - may help - still had it in my console history (89.42 KB, text/plain)
2004-09-03 00:34 UTC, _ tboudreau 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2004-09-02 15:57:56 UTC 
I was editing org.openide.awt.Toolbar, and tried 
to invoke code completion with this.addD[ctrl-
space].

CPU usage went to 100%, and I got a fascinating 
thread dump - tons of threads all blocked in 
AbstractLookup.enterStorage().  Today's build.

I had used code completion successfully a few 
times earlier in the session, so it's probably 
random.
Comment 1 _ tboudreau 2004-09-02 15:58:41 UTC 
Created attachment 17329 [details]
Thread dump
Comment 2 _ tboudreau 2004-09-02 16:08:06 UTC 
Just happened again while just typing, so not code completion 
related.
Comment 3 _ tboudreau 2004-09-02 16:09:06 UTC 
Hmm, interesting - it recovered (it didn't the first time - I gave 
it several minutes to do so).
Comment 4 Petr Nejedly 2004-09-02 16:36:30 UTC 
Tim, it´s pity you have not attached the full thread dump.
This way it is hard to guess what is going on.
Anyway, please file another bug for java module/JavaparserGlue
for abusing the default RqP...

Need to see the rest of TD, but the Lookup is probably innocent here..
Comment 5 _ ttran 2004-09-02 17:29:25 UTC 
I saw a similar thread dump in bug filed agaist java/refactoring. 
don't remember the bug number though
Comment 6 _ tboudreau 2004-09-03 00:34:41 UTC 
Created attachment 17338 [details]
More thread dump - may help - still had it in my console history
Comment 7 Jaroslav Tulach 2004-09-03 08:12:31 UTC 
1. the enourmous number of theads is caused by JavaParserGlue using
RequestProcessor.getDefault(). Very likely it is not what is wanted.

2. Lookup is being invoked by CompatibleNode and seems to be doing
what it should. No stacktrace seems to indicate anything else.

3. If the CPU usage is 100% than it is hardly a deadlock.
Comment 8 Jan Becicka 2004-09-03 08:41:24 UTC 
We know about this problem and Tomas even has a fix for it. We are
testing it from Wednesday.
Tomasi, the fix works for me. Can you commit it to trunk? Thanks.
Comment 9 Tomas Hurka 2004-09-03 16:13:21 UTC 

*** This issue has been marked as a duplicate of 48158 ***