[cmwright@rampageinc.com]

I have been seeing a repeating variety of errors with M8 on Windows7 64bit.

And, to be clear here, I am using the 32bit M8 running on Sun’s 32bit jvm (1.6.0_13)
eclipse.buildId=unknown
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

What I am seeing is this:

An error dialog stating
“Multiple problems have occurred”
Background Indexer Crash Recovery
unable to create new native thread

and then, after dismissing that dialog:
“Internal Error”
An internal error occurred while showing an internal error.
You are recommended to exit the workbench…

Now, this *always* happens when either opening a closed project *or* importing a new project from svn.

It also happens randomly during the day.

Starting M8 with -clean results in this:

An internal error occurred during: “Open Project”.
unable to create new native thread

The error log has this corresponding entry:

!SESSION 2010-03-18 15:02:14.778 ———————————————–
eclipse.buildId=unknown
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.equinox.registry 2 0 2010-03-18 15:02:24.726
!MESSAGE The extensions and extension-points from the bundle “org.eclipse.epf.richtext” are ignored. The bundle is not marked as singleton.

!ENTRY org.eclipse.equinox.p2.repository 4 0 2010-03-18 15:02:25.325
!MESSAGE ProvisioningEventBus could not be obtained. Metadata caches may not be cleaned up properly.

!ENTRY org.eclipse.jface 2 0 2010-03-18 15:02:31.968
!MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2010-03-18 15:02:31.968
!MESSAGE A conflict occurred for CTRL+F9:
Binding(CTRL+F9,
ParameterizedCommand(Command(org.eclipse.mylyn.tasks.ui.command.activateTask,Activate Task,
,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(CTRL+F9,
ParameterizedCommand(Command(RunSQLAction,Run SQL,
Run SQL,
Category(org.eclipse.ui.category.edit,Edit,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
!SUBENTRY 1 org.eclipse.jface 2 0 2010-03-18 15:02:31.968
!MESSAGE A conflict occurred for SHIFT+DEL:
Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.eclipse.datatools.sqltools.result.removeAllInstances,Remove All Visible Results,
,
Category(org.eclipse.datatools.sqltools.result.category,SQL Results View,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.eclipse.ui.edit.cut,Cut,
Cut the selection to the clipboard,
Category(org.eclipse.ui.category.edit,Edit,null,true),
org.eclipse.ui.internal.handlers.WidgetMethodHandler@1ecdb1b,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.dialogAndWindow,,,system)
Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.topcased.modeler.deleteModelObject,Delete From Model,
Allows the user to delete the selected graph element and its associated model element in a Topcased editor.,
Category(org.eclipse.ui.category.edit,Edit,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)

!ENTRY org.eclipse.core.jobs 4 2 2010-03-18 15:05:06.320
!MESSAGE An internal error occurred during: “Building workspace”.
!STACK 0
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:597)
at org.tmatesoft.svn.core.javahl.SVNClientImplTracker.registerClient(SVNClientImplTracker.java:38)
at org.tmatesoft.svn.core.javahl.SVNClientImpl.newInstance(SVNClientImpl.java:192)
at org.tmatesoft.svn.core.javahl.SVNClientImpl.newInstance(SVNClientImpl.java:185)
at org.tigris.subversion.svnclientadapter.svnkit.SvnKitClientAdapter.<init>(SvnKitClientAdapter.java:56)
at org.tigris.subversion.clientadapter.svnkit.Activator.getAdapter(Activator.java:74)
at org.tigris.subversion.clientadapter.Activator.getClientAdapter(Activator.java:70)
at org.tigris.subversion.subclipse.core.SVNClientManager.getAdapter(SVNClientManager.java:142)
at org.tigris.subversion.subclipse.core.SVNClientManager.getSVNClient(SVNClientManager.java:92)
at org.tigris.subversion.subclipse.core.SVNProviderPlugin.getSVNClient(SVNProviderPlugin.java:425)
at org.tigris.subversion.subclipse.core.status.NonRecursiveStatusUpdateStrategy.statusesToUpdate(NonRecursiveStatusUpdateStrategy.java:53)
at org.tigris.subversion.subclipse.core.status.StatusCacheManager.refreshStatus(StatusCacheManager.java:264)
at org.tigris.subversion.subclipse.core.resourcesListeners.SyncFileChangeListener$ChangesCollector.refreshProjectFolders(SyncFileChangeListener.java:320)
at org.tigris.subversion.subclipse.core.resourcesListeners.SyncFileChangeListener$1.run(SyncFileChangeListener.java:298)
at org.tigris.subversion.subclipse.core.SVNProviderPlugin$6.run(SVNProviderPlugin.java:498)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.tigris.subversion.subclipse.core.SVNProviderPlugin.run(SVNProviderPlugin.java:493)
at org.tigris.subversion.subclipse.core.resourcesListeners.SyncFileChangeListener$ChangesCollector.refreshChangedResources(SyncFileChangeListener.java:296)
at org.tigris.subversion.subclipse.core.resourcesListeners.SyncFileChangeListener.resourceChanged(SyncFileChangeListener.java:147)
at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:297)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:136)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.eclipse.core.jobs 4 2 2010-03-18 15:05:06.322
!MESSAGE An internal error occurred during: “Open Project”.
!STACK 0
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:597)
at org.eclipse.core.internal.jobs.WorkerPool.jobQueued(WorkerPool.java:145)
at org.eclipse.core.internal.jobs.JobManager.schedule(JobManager.java:1001)
at org.eclipse.core.internal.jobs.InternalJob.schedule(InternalJob.java:391)
at org.eclipse.core.runtime.jobs.Job.schedule(Job.java:435)
at com.google.gdt.eclipse.core.BuilderUtilities.revalidateCompilationUnits(BuilderUtilities.java:170)
at com.google.gwt.eclipse.core.clientbundle.ClientBundleResourceChangeListener$1.visit(ClientBundleResourceChangeListener.java:154)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48)
at com.google.gwt.eclipse.core.clientbundle.ClientBundleResourceChangeListener.visitResourceDelta(ClientBundleResourceChangeListener.java:124)
at com.google.gwt.eclipse.core.clientbundle.ClientBundleResourceChangeListener.resourceChanged(ClientBundleResourceChangeListener.java:116)
at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1022)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

My config is this:

*** Date:
Thursday, March 18, 2010 2:57:07 PM EDT

** System properties:
OS=WindowsVista
OS version=6.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 8.0
Build id: 8.0-20091120

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 8.0
Build id: 8.0-20091120

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Users\Clark\AppData\Local\Genuitec\MyEclipse 8.x Latest\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Users\Clark\AppData\Local\Genuitec\MyEclipse 8.x Latest\../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\Users\Clark\AppData\Local\Genuitec\MyEclipse 8.x Latest\../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/Users/Clark/AppData/Local/Genuitec/MyEclipse 8.x Latest
-configuration
configuration
-vm
C:/Users/Clark/AppData/Local/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll

the myeclipse.ini is this:

-startup
../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
–launcher.library
../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-install
C:/Users/Clark/AppData/Local/Genuitec/MyEclipse 8.x Latest
-vm
C:/Users/Clark/AppData/Local/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll
-configuration
configuration
-vmargs
-Xms1024m
-Xmx1024m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=128m

Any ideas?

– Clark

[support-joy]

Clark,

I am afraid ME is currently not supported on x64 bit on Windows OS.

Sorry for the inconvenience.

[cmwright@rampageinc.com]

Joy,

As a paying customer, I find this response unacceptable.

Since we are basing our development on Windows 7 64bit, and have purchased licenses from Genuitec for that development, I have a couple of questions for you:

1. We are running on top of the 32bit Sun 1.6 jvm which supports 64bit Windows 7. Why do you not support this?
2. After reviewing the download, release notes, and new and noteworthy, there is no mention that 64bit windows os is not supported. So aside from this thread, where is the official statement of this?
3. When is Genuitec planning on providing support for 64bit Windows 7?

– Clark.

[Ton Huisman]

ME on Windows 7 x64 (or Vista x64 for that matter) works fine since ME 7.0x release, when used with a 32 bit Sun JVM/JDK. I have been using it on this platform for the last 2 years without major issues, but the ME 6.x range, based on Eclipse 3.4, did have several display ‘difficulties’, that where eventually solved when Eclipse 3.5 became the base of ME.
You may have installed a plugin that is not 100% compatible with parts of ME, or with the Eclipse 3.5.1 underground, or your entire install could be flaky. I’d try a re-install (first removing all of ME and Pulse) and then re-install using the Al-in-One ME 8.0 GA installer.

HTH
Ton

[Brian Fernandes]

Clark,

Sorry for the mis-communication, MyEclipse is definitely supported on Windows 7 64bit, we don’t have a build that works on the 64bit version of Eclipse, it will only work on the 32bit version – which is how you already have it working. We are also working on making a 64bit build available over the next few months. As Ton stated, there were issues with 64bit stability in past versions, but they should be cleared with this version of ME.

The only item of note I see in your logs is that you are running out of memory – and both times with plugins that are not from MyEclipse – one trace indicates GWT and the other SVN. Though, in the event of a low memory situation, you could fail on practically everything, we don’t know what exactly is causing the problem.

I noticed you set your memory settings at 1024, do you actually need that much memory – do you have very large or many projects in your workspace? In some cases where the value is too high, it could be silently ignored by the VM, you could try taking Xmx / Xms down to 768m if you don’t really need 1024.

Some other suggestions – especially if you can easily replicate the problem all the time – is to install the SVN plugin and / or the GWT plugin and see if your experience improves during the checkout / open project. That would help narrow down the cause of this problem. You can then re-add them and make sure you are using the latest versions of these plugins. As an alternative to Subclipse, you could try using Subversive for SVN support.

Hope this helps, please let us know how it goes.

[Author]

Posts