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 183857 - "Active Reference Queue Daemon" is constantly running
Summary: "Active Reference Queue Daemon" is constantly running
Status: CLOSED DUPLICATE of bug 183864
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 3.x
Hardware: PC Solaris
: P2 normal (vote)
Assignee: issues@performance
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-12 03:42 UTC by ivan
Modified: 2011-05-25 11:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ActiveReferenceQueue stack tarce (1.04 KB, text/plain)
2010-04-12 03:45 UTC, ivan 		Details
Ibid (1.04 KB, text/plain)
2010-04-12 03:45 UTC, ivan 		Details
Ibid (1.04 KB, text/plain)
2010-04-12 03:46 UTC, ivan 		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 ivan 2010-04-12 03:42:34 UTC 
A recent (Apr 6-7?) build of NB constantly runs the 
"Active Reference Queue Daemon" consuming all of a whole CPU's
cycles. My machine would've been unusable if it didn't have two CPU's.
I'll attach a few sample stack traces ...
Comment 1 ivan 2010-04-12 03:45:27 UTC 
Created attachment 97039 [details]
ActiveReferenceQueue stack tarce
Comment 2 ivan 2010-04-12 03:45:51 UTC 
Created attachment 97040 [details]
Ibid
Comment 3 ivan 2010-04-12 03:46:12 UTC 
Created attachment 97041 [details]
Ibid
Comment 4 ivan 2010-04-12 05:38:17 UTC 
This doesn't always happen.
From Apr 6-7 I hadn't seen this til today.
The main thing that changed today was that I opened the cnd.kit
project (in my attempts to experiment regarding the thread
"FileUtil-Refresh-All is killing me".)
I exited and restarted NB but still had ARQ hog the cpu.
I worked for a while with this and then closed cnd.kit.
The hogging went away.
I re-opened cnd.kit but the hogging didn't come back.
So, nothing very conclusive unfortunately ...
Comment 5 Stanislav Aubrecht 2010-04-12 10:52:00 UTC 
perf team, pls investigate, thanks
Comment 6 Jaroslav Tulach 2010-04-12 11:02:58 UTC 
Also reported as bug 183864

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