Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319895

Summary: Apparent deadlock in service registry logic
Product: [Eclipse Project] Equinox Reporter: Ben Vitale <bvitale3002>
Component: CompendiumAssignee: equinox.compendium-inbox <equinox.compendium-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: tjwatson
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Series of dumps while Eclipse was at 100% CPU none

Description Ben Vitale CLA 2010-07-14 14:29:07 EDT 
Build Identifier: 20100617-1415

Eclipse 3.6, Windows 7.
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)

I do not have good steps to reproduce this, but it seems to be happening quite frequently for me since I upgraded my JRE to the latest.

I will attach a series of thread dumps which appear to point in this general vicinity:

	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:728)
	- locked <0x000000000af16bc8> (a java.util.HashMap)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:711)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:171)
	at org.eclipse.equinox.internal.app.EclipseAppDescriptor.refreshProperties(EclipseAppDescriptor.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppContainer.refreshAppDescriptors(EclipseAppContainer.java:470)
	- locked <0x000000000bb39050> (a java.lang.Object)
	at org.eclipse.equinox.internal.app.EclipseAppContainer.unlock(EclipseAppContainer.java:540)

Reproducible: Sometimes

Steps to Reproduce:
1. Launch Eclipse
2. Wait
Comment 1 Ben Vitale CLA 2010-07-14 14:33:12 EDT 
Created attachment 174324 [details]
Series of dumps while Eclipse was at 100% CPU
Comment 2 Thomas Watson CLA 2010-07-14 15:49:56 EDT 
Before spending much time on this, can you rule out bug319514

The workaround for that bug is to add the following to the end of the eclipse.ini file:

-XX:MaxPermSize=256m
Comment 3 Ben Vitale CLA 2010-07-14 16:03:32 EDT 
(In reply to comment #2)
> Before spending much time on this, can you rule out bug319514
> 

Looks like my problem. Thanks.

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