Bug 110166 - [DND] no eclipse start - Cannot initialize Drop
Summary: [DND] no eclipse start - Cannot initialize Drop
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact: Kevin Barnes CLA
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2005-09-21 08:49 EDT by frank musolf CLA
Modified: 2020-03-26 02:00 EDT (History)
7 users (show)

See Also:


Attachments
Eclipse log file (8.68 KB, text/plain)
2009-11-05 07:02 EST, Andreas CLA
no flags Details
Azureus / Vuze log file (18.71 KB, text/plain)
2009-11-05 07:03 EST, Andreas CLA
no flags Details
Eclipse .metadata/.log file (3.69 KB, text/plain)
2009-12-05 12:26 EST, Netrosis CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description frank musolf CLA 2005-09-21 08:49:54 EDT
hi 

eclipse 3.2M1 is fresh installed and produce only a exception (Cannot initialize 
Drop) by start. behavior is since i have to kill eclipse while hanging complete. 
i have install eclipse complete new without any plugins and restarted my system. 
old workspace directory is removed before i start eclipse.

what can i do ?

frank 

!SESSION 2005-09-21 14:40:01.453 -----------------------------------------------
eclipse.buildId=I20050811-1530
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 2005-09-21 14:40:15.203
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: Cannot initialize Drop
	at org.eclipse.swt.dnd.DND.error(DND.java:247)
	at org.eclipse.swt.dnd.DND.error(DND.java:208)
	at org.eclipse.swt.dnd.DropTarget.<init>(DropTarget.java:137)
	at org.eclipse.ui.internal.EditorSashContainer.
addDropSupport(EditorSashContainer.java:433)
	at org.eclipse.ui.internal.EditorSashContainer.
createControl(EditorSashContainer.java:425)
	at org.eclipse.ui.internal.EditorAreaHelper.<init>(EditorAreaHelper.java:41)
	at org.eclipse.ui.internal.WorkbenchPage.init(WorkbenchPage.java:2050)
	at org.eclipse.ui.internal.WorkbenchPage.<init>(WorkbenchPage.java:509)
	at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.java:
678)
	at org.eclipse.ui.internal.Workbench.busyOpenWorkbenchWindow(Workbench.java:
669)
	at org.eclipse.ui.internal.Workbench.doOpenFirstTimeWindow(Workbench.java:1317)
	at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1315)
	at org.eclipse.ui.internal.Workbench$15.run(Workbench.java:1233)
	at org.eclipse.ui.internal.Workbench.runStartupWithProgress(Workbench.java:
1258)
	at org.eclipse.ui.internal.Workbench.openFirstTimeWindow(Workbench.java:1231)
	at org.eclipse.ui.internal.WorkbenchConfigurer.
openFirstTimeWindow(WorkbenchConfigurer.java:190)
	at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.
java:706)
	at org.eclipse.ui.internal.Workbench.init(Workbench.java:1034)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1671)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.
java:226)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:338)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)
Comment 1 Olivier Thomann CLA 2005-09-21 08:51:41 EDT
Move to Platform/SWT
Comment 2 Billy Biggs CLA 2005-09-27 00:02:41 EDT
VI, any ideas?
Comment 3 Veronika Irvine CLA 2005-09-27 09:46:49 EDT
Have you seen this repeatedly or was this a one time thing?
The error occurs because the operating system will not allow us to lock the 
object to ensure that it stays in memory.  This is quite bizarre.
Comment 4 Billy Biggs CLA 2005-10-17 19:16:12 EDT
This was posted to the eclipse.newcomer newsgroup.  Note the NL=zh_CN
and the original poster here reported it with NL=de_DE.  Does this
have something to do with it?

------
Sometimes,my Eclipse3.0 can't be started.From workspace->.metadata->.log,I found it always said 
something as follows:

!SESSION &#21313;&#26376; 12, 2005 15:16:29.546 
----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN
!ENTRY org.eclipse.osgi &#21313;&#26376; 12, 2005 15:16:29.578
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: Cannot initialize Drop
at org.eclipse.swt.dnd.DND.error(DND.java:220)
at org.eclipse.swt.dnd.DND.error(DND.java:181)
at org.eclipse.swt.dnd.DropTarget.<init>(DropTarget.java:133)
at org.eclipse.ui.internal.EditorSashContainer.addDropSupport(EditorSashContainer.java:360)
at org.eclipse.ui.internal.EditorSashContainer.createControl(EditorSashContainer.java:354)
at org.eclipse.ui.internal.PartSashContainer.createControl(PartSashContainer.java:427)
at org.eclipse.ui.internal.PerspectiveHelper.activate(PerspectiveHelper.java:156)
at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:718)
at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:1984)
at org.eclipse.ui.internal.WorkbenchWindow$4.run(WorkbenchWindow.java:1787)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:1774)
at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1344)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1216)
at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1183)
at org.eclipse.ui.internal.Workbench$13.run(Workbench.java:1094)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:608)
at org.eclipse.core.runtime.Platform.run(Platform.java:758)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1027)
at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:167)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:652)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:817)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1311)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:253)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:97)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:307)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:256)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:638)
at org.eclipse.core.launcher.Main.main(Main.java:622)

Q:How to solve this problem??
Thanks!


Comment 5 Jacek Pospychala CLA 2007-06-27 12:28:58 EDT
Hello,
it's been quite some time since this bug was opened, 
do you have any update on this "Cannot initialize Drop" problem? Did the problem stopped to occur?
It would be very helpful if you had any findings.

btw, is there anything special about your hardware, eg. is it amd64, or dual-core? 

Looks like there is couple of somehow related bugs, that are still NEW:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=161893
https://bugs.eclipse.org/bugs/show_bug.cgi?id=110166
https://bugs.eclipse.org/bugs/show_bug.cgi?id=98773
https://bugs.eclipse.org/bugs/show_bug.cgi?id=76449
https://bugs.eclipse.org/bugs/show_bug.cgi?id=42292
Comment 6 Jacek Pospychala CLA 2007-07-26 10:55:18 EDT
Ok I got it once only and didn't occured again.
Comment 7 Andreas CLA 2009-11-05 07:00:53 EST
I am having this problem since a couple of days. Running W7x64 RTM, Eclipse 3.5 SR1 (the "for Java EE Developers" package) and Java 6 Update 17 (16 previously).

I had not changed my Eclipse, which ran fine, and Java configuration when the problem started occurring. Running a fresh copy of Eclipse and reinstalling Java changed nothing.

Azureus (aka Vuze) is malfunctioning as well, apparently due to the same bug.
Comment 8 Andreas CLA 2009-11-05 07:02:13 EST
Created attachment 151399 [details]
Eclipse log file
Comment 9 Andreas CLA 2009-11-05 07:03:53 EST
Created attachment 151400 [details]
Azureus / Vuze log file
Comment 10 Netrosis CLA 2009-12-05 12:26:35 EST
Created attachment 153864 [details]
Eclipse .metadata/.log file

I've added my own .log file.
Running Vista x64 Ultimate,
with a 32bit Sun JRE, and 32bit Eclipse.
It works fine on my other computer running WindowsXP.

Eclipse was working fine, until around September/October 2009 and I believe what was after a Java update, these errors started happening. Tried rolling back to the old Java, trying a JDK instead, fresh installations of Eclipse and Java, still nothing. I even tried rolling back to Vista Service Pack 1, still receiving the error when the loading bar appears on the splash screen.

Almost prepared to reinstall Vista if it means I can get Eclipse PDT working again.
Comment 11 Leo Ufimtsev CLA 2017-08-03 12:31:00 EDT
This is a one-off bulk update. (The last one in the triage migration).

Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process:
https://wiki.eclipse.org/SWT/Devel/Triage

See Bug 518478 for details.

Tag for notification/mail filters:
@TriageBulkUpdate