Eclipse Community Forums: Java Development Tools (JDT) » Eclipse 3.0: 100% CPU all the time

Home » Language IDEs » Java Development Tools (JDT) » Eclipse 3.0: 100% CPU all the time

Eclipse 3.0: 100% CPU all the time [message #85031]

Tue, 12 August 2003 14:56

Eclipse User

Originally posted by: no.email.please

I tried various builds of the 3.0 line (3.0M1, 3.0M2, i20030723 and
i20030806) and they all have this same problem for me: even when I am
no longer using Eclipse (and it's iconified), it keeps my CPU at 100%
with a javaw process.

I use 2.1.1 every day and I never see this problem.

Has anyone else seen this?

--
Cedric
http://beust.com/weblog

Re: Eclipse 3.0: 100% CPU all the time [message #85258 is a reply to message #85031]

Wed, 13 August 2003 04:41

Eclipse User

Can you file a bug report with this? Please specify the platform
(windows, linux..) you're working on.

A way to find out what's going on is to start eclipse from the command
line with
java Xmx512M -cp startup.jar org.eclipse.core.launcher.Main -update
-application org.eclipse.ui.workbench -data c:\workspaces\eclipse-testpass

and use CTRL break to see a stack trace of all threads currently running
(that's under windows, not sure if this works the same way for linux)

Martin

news.eclipse.org wrote:
> I tried various builds of the 3.0 line (3.0M1, 3.0M2, i20030723 and
> i20030806) and they all have this same problem for me: even when I am
> no longer using Eclipse (and it's iconified), it keeps my CPU at 100%
> with a javaw process.
>
> I use 2.1.1 every day and I never see this problem.
>
> Has anyone else seen this?
>

Re: Eclipse 3.0: 100% CPU all the time [message #85540 is a reply to message #85031]

Wed, 13 August 2003 15:31

Eclipse User

news.eclipse.org wrote:
> I tried various builds of the 3.0 line (3.0M1, 3.0M2, i20030723 and
> i20030806) and they all have this same problem for me: even when I am
> no longer using Eclipse (and it's iconified), it keeps my CPU at 100%
> with a javaw process.
>
> I use 2.1.1 every day and I never see this problem.
>
> Has anyone else seen this?
>

I get a somewhat similar problem, both with 3.0M2, and 3.0I20030806.
Eclipse will perform normally for a while. Then it gets into a state
where on some operations (Ctrl-Shift-T, find type is one that seems to
trigger it a lot), it will basically just freeze for anywhere from 30
seconds to a couple of minutes. During this time, the cpu usage is
almost 100%. Once it starts doing this for Ctrl-Shift-T, it will always
keep doing it, until I exit and come back in. There are also other
operations which seem to cause the freeze, but Ctrl-Shift-T is the most
common one. There also seems to be the same pause on exiting Eclipse
sometimes, except in that case it sometimes never exits at all, and I
have to kill it.

One consideration is that I installed this version of Eclipse to use a
workspace from a 2.1.1 installation, ie I did not start from scratch. I
did this since I have a lot of projects in the workspace, and it is such
an incredible pain to import a larger number of existing projects form
the filesystem. Once a new Integration build is out I will perhaps try a
clean install, where I start with an empty workspace, and go through the
normal import process.

Re: Eclipse 3.0: 100% CPU all the time [message #85648 is a reply to message #85258]

Wed, 13 August 2003 23:03

Eclipse User

Originally posted by: no.email.please

Martin Aeschlimann wrote:
> Can you file a bug report with this? Please specify the platform
> (windows, linux..) you're working on.
>
> A way to find out what's going on is to start eclipse from the command
> line with
> java Xmx512M -cp startup.jar org.eclipse.core.launcher.Main -update
> -application org.eclipse.ui.workbench -data c:\workspaces\eclipse-testpass
>
> and use CTRL break to see a stack trace of all threads currently running
> (that's under windows, not sure if this works the same way for linux)

Okay, after a few hours, I got Eclipse to do the same thing again. I
included a full thread dump below and a quick look shows that only the
following thread is potentially busy at this point:

"Thread-8" prio=7 tid=0x272DA7F0 nid=0xcbc runnable [2872f000..2872fd8c]
at
org.eclipse.core.internal.properties.StoreKey.readNullTermin ated(StoreKey.java:140)

All the others are Object.wait() or Thread.sleep().

I tried to look up the source myself but I didn't find any
org/eclipse/core/internal/resources directory at
http://dev.eclipse.org/viewcvs/index.cgi/. I suppose I am looking at
the wrong tree.

I am using i20030806.

Any idea what's going on?

--
Cedric
http://beust.com/weblog

(full thread dump below)

Full thread dump Java HotSpot(TM) Client VM (1.4.1_02-ea-b01 mixed mode):

"Snapshot" prio=7 tid=0x27320410 nid=0xda4 in Object.wait()
[2876f000..2876fd8c]

at java.lang.Object.wait(Native Method)
- waiting on <10B433C8> (a
org.eclipse.core.internal.resources.DelayedSn
apshotRunnable)
at
org.eclipse.core.internal.resources.DelayedSnapshotRunnable. run(Delay
edSnapshotRunnable.java:40)
- locked <10B433C8> (a
org.eclipse.core.internal.resources.DelayedSnapsh
otRunnable)
at java.lang.Thread.run(Thread.java:536)

"Thread-8" prio=7 tid=0x272DA7F0 nid=0xcbc runnable [2872f000..2872fd8c]
at
org.eclipse.core.internal.properties.StoreKey.readNullTermin ated(Stor
eKey.java:140)
at
org.eclipse.core.internal.properties.StoreKey.initializeObje cts(Store
Key.java:123)
at
org.eclipse.core.internal.properties.StoreKey.<init>(StoreKey.java:31
)
at
org.eclipse.core.internal.properties.PropertyStore.visitProp ertyAt(Pr
opertyStore.java:437)
at
org.eclipse.core.internal.properties.PropertyStore.recordsMa tching(Pr
opertyStore.java:308)
at
org.eclipse.core.internal.properties.PropertyStore.get(Prope rtyStore.
java:171)
at
org.eclipse.core.internal.properties.PropertyManager.getProp erty(Prop
ertyManager.java:108)
- locked <0A42C610> (a
org.eclipse.core.internal.properties.PropertyStor
e)
at
org.eclipse.core.internal.resources.Resource.getPersistentPr operty(Re
source.java:880)
at
net.sourceforge.perforce.core.internal.api.PerforceServerMan ager.getP
erforceServer(PerforceServerManager.java:219)
at
net.sourceforge.perforce.core.resources.LocalResource.create FromResou
rce(LocalResource.java:53)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:134)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.resources.LocalResource.isIgno red(Local
Resource.java:135)
at
net.sourceforge.perforce.core.internal.P4TeamProvider.isIgno red(P4Tea
mProvider.java:356)
at
net.sourceforge.perforce.core.internal.events.AddDeleteMoveL istener.c
reateNecessaryMarkers(AddDeleteMoveListener.java:388)
at
net.sourceforge.perforce.core.internal.events.AddDeleteMoveL istener.r
esourceStateChanged(AddDeleteMoveListener.java:225)
at
net.sourceforge.perforce.core.PerforceCorePlugin$3.run(Perfo rceCorePl
ugin.java:442)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatfo
rm.java:1015)
at org.eclipse.core.runtime.Platform.run(Platform.java:420)
at
net.sourceforge.perforce.core.PerforceCorePlugin.broadcastRe sourceSta
teChanges(PerforceCorePlugin.java:451)
at
net.sourceforge.perforce.core.PerforceSynchronizer$1.run(Per forceSync
hronizer.java:1015)
at java.lang.Thread.run(Thread.java:536)

"org.eclipse.jdt.internal.ui.text.JavaReconciler" daemon prio=5
tid=0x272031D8 n
id=0xcf0 in Object.wait() [286af000..286afd8c]
at java.lang.Object.wait(Native Method)
at
org.eclipse.jface.text.reconciler.AbstractReconciler$Backgro undThread
..run(AbstractReconciler.java:161)
- locked <0B700CC8> (a
org.eclipse.jface.text.reconciler.DirtyRegionQueu
e)

"Worker-4" prio=7 tid=0x2724CFD8 nid=0xdf8 in Object.wait()
[2866f000..2866fd8c]

at java.lang.Object.wait(Native Method)
- waiting on <051F5600> (a
org.eclipse.core.internal.jobs.WorkerPool)
at
org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.j ava:97)
- locked <051F5600> (a org.eclipse.core.internal.jobs.WorkerPool)
at
org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPoo l.java:13
0)
- locked <051F5600> (a org.eclipse.core.internal.jobs.WorkerPool)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:73)

"org.eclipse.jdt.internal.ui.text.JavaReconciler" daemon prio=2
tid=0x271564A8 n
id=0xab8 runnable [2753f000..2753fd8c]
at java.lang.Object.wait(Native Method)
at
org.eclipse.jface.text.reconciler.AbstractReconciler$Backgro undThread
..run(AbstractReconciler.java:161)
- locked <0B700D78> (a
org.eclipse.jface.text.reconciler.DirtyRegionQueu
e)

"Perforce Decorator" prio=7 tid=0x26E1D648 nid=0x758 in Object.wait()
[27c5f000.
..27c5fd8c]
at java.lang.Object.wait(Native Method)
- waiting on <0A8C4F90> (a
net.sourceforge.perforce.ui.PerforceDecorator
)
at java.lang.Object.wait(Object.java:426)
at
net.sourceforge.perforce.ui.PerforceDecorator.next(PerforceD ecorator.
java:260)
- locked <0A8C4F90> (a
net.sourceforge.perforce.ui.PerforceDecorator)
at
net.sourceforge.perforce.ui.PerforceDecorationRunnable.run(P erforceDe
corationRunnable.java:122)
at java.lang.Thread.run(Thread.java:536)

"Perforce Background Update Monitor" prio=7 tid=0x27DA9618 nid=0xeac
waiting on
condition [27c1f000..27c1fd8c]
at java.lang.Thread.sleep(Native Method)
at
net.sourceforge.perforce.core.internal.BackgroundUpdateRunna ble.run(B
ackgroundUpdateRunnable.java:114)
at java.lang.Thread.run(Thread.java:536)

"Perforce Connection Monitor" prio=7 tid=0x27149CD0 nid=0xee8 waiting on
conditi
on [27bdf000..27bdfd8c]
at java.lang.Thread.sleep(Native Method)
at
net.sourceforge.perforce.core.internal.ConnectionMonitorRunn able.run(
ConnectionMonitorRunnable.java:81)
at java.lang.Thread.run(Thread.java:536)

"org.eclipse.jdt.internal.ui.text.JavaReconciler" daemon prio=2
tid=0x26F77CD8 n
id=0x76c in Object.wait() [2785f000..2785fd8c]
at java.lang.Object.wait(Native Method)
- waiting on <0A7A4BD8> (a
org.eclipse.jface.text.reconciler.DirtyRegion
Queue)
at
org.eclipse.jface.text.reconciler.AbstractReconciler$Backgro undThread
..run(AbstractReconciler.java:161)
- locked <0A7A4BD8> (a
org.eclipse.jface.text.reconciler.DirtyRegionQueu
e)

"Java indexing" daemon prio=4 tid=0x009CB8C0 nid=0xc98 in Object.wait()
[2781f00
0..2781fd8c]
at java.lang.Object.wait(Native Method)
- waiting on <0A6BB6D8> (a
org.eclipse.jdt.internal.core.search.indexing
..IndexManager)
at java.lang.Object.wait(Object.java:426)
at
org.eclipse.jdt.internal.core.search.processing.JobManager.r un(JobMan
ager.java:358)
- locked <0A6BB6D8> (a
org.eclipse.jdt.internal.core.search.indexing.Ind
exManager)
at java.lang.Thread.run(Thread.java:536)

"Signal Dispatcher" daemon prio=10 tid=0x009A7F58 nid=0xb4c waiting on
condition
[0..0]

"Finalizer" daemon prio=9 tid=0x009A4560 nid=0x91c in Object.wait()
[26cbf000..2
6cbfd8c]
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked <051D5D80> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:1 59)

"Reference Handler" daemon prio=10 tid=0x009EDC48 nid=0xd98 in
Object.wait() [95
f000..95fd8c]
at java.lang.Object.wait(Native Method)
- waiting on <051D5DE8> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:426)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java: 113)
- locked <051D5DE8> (a java.lang.ref.Reference$Lock)

"main" prio=7 tid=0x00036400 nid=0xd4 runnable [7f000..7fc40]
at org.eclipse.swt.internal.win32.OS.WaitMessage(Native Method)
at org.eclipse.swt.widgets.Display.sleep(Display.java:2485)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1681)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1663)
at
org.eclipse.core.internal.boot.InternalBootLoader.run(Intern alBootLoa
der.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)

"VM Thread" prio=5 tid=0x009EC9C0 nid=0xd9c runnable

"VM Periodic Task Thread" prio=10 tid=0x009A6C48 nid=0xbac waiting on
condition

"Suspend Checker Thread" prio=10 tid=0x009A7508 nid=0xb94 runnable

>
> Martin
>
>
> news.eclipse.org wrote:
>
>> I tried various builds of the 3.0 line (3.0M1, 3.0M2, i20030723 and
>> i20030806) and they all have this same problem for me: even when I am
>> no longer using Eclipse (and it's iconified), it keeps my CPU at 100%
>> with a javaw process.
>>
>> I use 2.1.1 every day and I never see this problem.
>>
>> Has anyone else seen this?
>>
>

Re: Eclipse 3.0: 100% CPU all the time [message #85661 is a reply to message #85258]

Wed, 13 August 2003 23:03

Eclipse User

Originally posted by: cbeust.bea.com

Martin Aeschlimann wrote:
> Can you file a bug report with this? Please specify the platform
> (windows, linux..) you're working on.
>
> A way to find out what's going on is to start eclipse from the command
> line with
> java Xmx512M -cp startup.jar org.eclipse.core.launcher.Main -update
> -application org.eclipse.ui.workbench -data c:\workspaces\eclipse-testpass
>
> and use CTRL break to see a stack trace of all threads currently running
> (that's under windows, not sure if this works the same way for linux)

Okay, after a few hours, I got Eclipse to do the same thing again. I
included a full thread dump below and a quick look shows that only the
following thread is potentially busy at this point:

"Thread-8" prio=7 tid=0x272DA7F0 nid=0xcbc runnable [2872f000..2872fd8c]
at
org.eclipse.core.internal.properties.StoreKey.readNullTermin ated(StoreKey.java:140)

All the others are Object.wait() or Thread.sleep().

I tried to look up the source myself but I didn't find any
org/eclipse/core/internal/resources directory at
http://dev.eclipse.org/viewcvs/index.cgi/. I suppose I am looking at
the wrong tree.

I am using i20030806.

Any idea what's going on?

--
Cédric
http://beust.com/weblog

Re: Eclipse 3.0: 100% CPU all the time [message #88391 is a reply to message #85540]

Fri, 22 August 2003 15:14

Eclipse User

I'm having a similar problem, but I wasn't sure that is was Eclipse. Eclipse
will just become unresponsive. The problem is that I don't see any specific
pattern to this. I've also noticed Eclipse takes a considerable amount of
time to start up, now between 18 and 20 seconds. I using these options
C:\eclipse\eclipse.exe -data c:/work -vmargs -Xmx256M. I'm not sure, if
Eclipse is at 100% CPU utilization. I've never bother check. I have gotten
the Windows "Program is not responding" error. I find that if I kill Eclipse
and start up again it works normally.

Regards,

Jeff Duska

Re: Eclipse 3.0: 100% CPU all the time [message #116566 is a reply to message #85031]

Wed, 12 November 2003 18:13

Eclipse User

Originally posted by: user.domain.invalid

I have seen the same issue with 2.1 and 2.1.1.

Matt

news.eclipse.org wrote:
> I tried various builds of the 3.0 line (3.0M1, 3.0M2, i20030723 and
> i20030806) and they all have this same problem for me: even when I am
> no longer using Eclipse (and it's iconified), it keeps my CPU at 100%
> with a javaw process.
>
> I use 2.1.1 every day and I never see this problem.
>
> Has anyone else seen this?
>

Previous Topic:	where to put plugins jar files
Next Topic:	Any way to keep Hierarchy view Horizontal View Orientation persistent?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jun 10 17:45:22 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter