is. I remembered it as out of handles, but that was a bit wrong. I
checked the process in the task manager when it was in the error
state. It isn't out of memory, and it's probably not out of handles.
The CPUs are also idle, so nothing is spinning.
The error from Eclipse is a dialog that says:
Multiple problems have occured (as title)
The error message is then, "unable to create new native thread".
Followed by a textfield that is displaying:
Collecting garbage
Collecting garbage
Unhandled event loop exception
unable to create new native thread
The eclipse error log can be seen below.
Eclipse was at that time taking about 400 MB of memory (of the 1300M
that I had assigned to the VM)
It took me about 10-15 minutes. All I did was editing one layout file,
switched between layout view, then edited the xml directly, changed
some properties through the property view, saved quite frequently,
even with compilation errors, and also tried keep editing while it was
saving.
This never happens when I write code in Eclipse.
!ENTRY org.eclipse.core.resources 8 2 2010-08-04 22:40:49.414
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.resources".
!STACK 1
org.eclipse.core.runtime.CoreException: 'aapt' error. Pre Compiler
Build aborted.
at
com.android.ide.eclipse.adt.internal.build.BaseBuilder.stopBuild(Unknown
Source)
at
com.android.ide.eclipse.adt.internal.build.PreCompilerBuilder.build(Unknown
Source)
at org.eclipse.core.internal.events.BuildManager
$2.run(BuildManager.java:627)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:
170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:
201)
at org.eclipse.core.internal.events.BuildManager
$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:
256)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:
309)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:
341)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:
140)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:
238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-08-04 22:40:49.414
!MESSAGE 'aapt' error. Pre Compiler Build aborted.
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-08-04 22:40:49.414
!MESSAGE 'aapt' error. Pre Compiler Build aborted.
!ENTRY org.eclipse.ui 4 0 2010-08-04 22:45:29.067
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Unknown Source)
at org.eclipse.jface.text.contentassist.AdditionalInfoController
$Timer.<init>(AdditionalInfoController.java:244)
at org.eclipse.jface.text.contentassist.AdditionalInfoController
$10.<init>(AdditionalInfoController.java:457)
at
org.eclipse.jface.text.contentassist.AdditionalInfoController.install(AdditionalInfoController.java:
457)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup.displayProposals(CompletionProposalPopup.java:
1198)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access
$23(CompletionProposalPopup.java:1157)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup
$2.run(CompletionProposalPopup.java:500)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:
70)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:
482)
at
org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:
1660)
at
org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:
446)
at org.eclipse.ui.texteditor.TextOperationAction
$1.run(TextOperationAction.java:131)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:
70)
at
org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction.java:
129)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:
185)
at
org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:
109)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:
476)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:
508)
at
org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:
169)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:
470)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:
824)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:
880)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:
569)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access
$3(WorkbenchKeyboard.java:510)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard
$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1208)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1368)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4053)
at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:346)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3946)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4619)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2411)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3501)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:
332)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:
493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:
113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:
194)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:
110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:
79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
368)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
179)
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.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
!ENTRY org.eclipse.core.jobs 4 2 2010-08-04 22:45:29.067
!MESSAGE An internal error occurred during: "Collecting garbage".
!STACK 0
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Unknown Source)
at java.lang.ref.Finalizer$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.lang.ref.Finalizer.forkSecondaryFinalizer(Unknown Source)
at java.lang.ref.Finalizer.runFinalization(Unknown Source)
at java.lang.Runtime.runFinalization0(Native Method)
at java.lang.Runtime.runFinalization(Unknown Source)
at java.lang.System.runFinalization(Unknown Source)
at org.eclipse.ui.internal.ide.application.IDEIdleHelper
$3.run(IDEIdleHelper.java:182)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!ENTRY org.eclipse.core.jobs 4 2 2010-08-04 22:45:29.068
!MESSAGE An internal error occurred during: "Collecting garbage".
!STACK 0
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Unknown Source)
at java.lang.ref.Finalizer$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.lang.ref.Finalizer.forkSecondaryFinalizer(Unknown Source)
at java.lang.ref.Finalizer.runFinalization(Unknown Source)
at java.lang.Runtime.runFinalization0(Native Method)
at java.lang.Runtime.runFinalization(Unknown Source)
at java.lang.System.runFinalization(Unknown Source)
at org.eclipse.ui.internal.ide.application.IDEIdleHelper
$3.run(IDEIdleHelper.java:182)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!ENTRY org.eclipse.core.resources 8 2 2010-08-04 22:45:53.521
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.resources".
!STACK 1
org.eclipse.core.runtime.CoreException: 'aapt' error. Pre Compiler
Build aborted.
at
com.android.ide.eclipse.adt.internal.build.BaseBuilder.stopBuild(Unknown
Source)
at
com.android.ide.eclipse.adt.internal.build.PreCompilerBuilder.build(Unknown
Source)
at org.eclipse.core.internal.events.BuildManager
$2.run(BuildManager.java:627)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:
170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:
201)
at org.eclipse.core.internal.events.BuildManager
$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:
256)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:
309)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:
341)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:
140)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:
238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-08-04 22:45:53.521
!MESSAGE 'aapt' error. Pre Compiler Build aborted.
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-08-04 22:45:53.521
!MESSAGE 'aapt' error. Pre Compiler Build aborted.
On 4 Aug, 18:54, DanH <danhi...@ieee.org> wrote:
> The Eclipse UI editor for Qt (which is similarly XML based) exhibits
> similar behavior -- some things you can do OK, but certain complex
> operations crash the editor (and sometimes Eclipse) with fair
> regularity. You learn to save your layouts frequently.
>
> Re poor performance in general, folks with Win64 should start Task
> Manager from time to time and note CPU usage. There is a bug rampant
> in Vista and not unlikely in Win7 that causes some sort of background
> activity causing 40-60% CPU utilization, with nothing else going on,
> and no process showing more than 2%. (System Idle Process shows
> 85-90%.) Folks with desktop boxes might miss this, but folks with
> laptops notice it because the CPU fan is running full bore when
> nothing is going on. Once this scenario starts you can only kill it
> by rebooting or hibernating.
>
> Another performance killer is the Windows indexing service.
>
> On Aug 4, 10:00 am, Kaj Bjurman <kaj.bjur...@gmail.com> wrote:
>
>
>
> > I think it was stated previously in this thread. The problem isn't
> > Eclipse. The problem is the Android plugin. I'm using Eclipse more
> > than 8h per day at work, and I don't have any problems there (I'm not
> > doing any Android development at work). I can also use Eclipse at home
> > without any problems if I never switch to the design view, or edit
> > Android xml files. Switching to design view or editing xml files means
> > that my Eclipse (tested several different versions) craches within one
> > hour. Often several times per hour, and it's always a related to a
> > memory problem, and it's due to leaking handles. Looks like it's
> > either directly related to editing, or generation of R.
>
> > (And I'm having a 64 bit machine with 8 GB of RAM)
>
> > On 4 Aug, 13:46, "Jonas Petersson" <jonas.peters...@xms.se> wrote:
>
> > > Ah, I think I can relate to that statement: for 95+% of the XML editing
> > > I referred to I used Eclipse itself, but like Kostya I stayed mostly in
> > > the XML view, only an occasional glance at the graphical layout since
> > > (at least for my cases) I decided the visual layout could not really be
> > > trusted. Showing it in the emulator was the only way to know that it
> > > actually worked as expected (yes, I had a rather picky spec to follow
> > > and in a few cases I actually pulled out emacs for significant
> > > restructuring, so I may have accidentally been lucky to manage for a week).
>
> > > Best / Jonas
>
> > > On 08/04/2010 11:55 AM, Kostya Vasilyev wrote:
>
> > > > This looks likely.
>
> > > > I can run Eclipse all day on a 4G Windows 64bit machine, but I edit my
> > > > layouts "by hand", without the visual editor.
>
> > > > 04.08.2010 11:00, Mystique пишет:
> > > >> I think there's some memory leak issue if editing XML files.
> > > >> I realise if I only open .java it is ok.
> > > >> So maybe a temp work around is to edit xml file with editor and open
> > > >> only .java in eclipse?
>
> > > >> On Aug 4, 10:17 am, Doug<beafd...@gmail.com> wrote:
> > > >>> The issue isn't what else is running on the computer. The issue is
> > > >>> that Eclipse gets into an unrecoverable state where it lags horribly
> > > >>> when switching between editors, at least on OSX. I can typically go 5
> > > >>> or 6 hours of steady use (more with intermittent use) until that state
> > > >>> kicks in for me (MacBook Pro, 4GB, 2.4GHz Core 2 Duo). Quitting other
> > > >>> apps at that point doesn't make any difference. The resource leak
> > > >>> explanation is the only one that makes sense given my observations,
> > > >>> which are daily since I do this to pay my mortgage.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment