comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Problems with IDL 8.1: the Development Enviroment is not starting
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Problems with IDL 8.1: the Development Enviroment is not starting [message #79995 is a reply to message #79853] Thu, 19 April 2012 08:55 Go to previous messageGo to previous message
lecacheux.alain is currently offline  lecacheux.alain
Messages: 325
Registered: January 2008
Senior Member
On 19 avr, 17:05, Helder <hel...@marchetto.de> wrote:
> Hi,
> I got IDL 8.1 in the middle of February. In the middle of March I had major crashes (using the new graphics...) and since the 15 of March IDL is not starting anymore. I obviously reported the bug to my local distributor and tried the proposed solutions:
> - basically reinstall
> - clean start of the DE (using the -clean keyword)
> - deleted the .idl directory
> - started the DE with the -outofprocess keyword
> - used the -data and -showlocation keywords
> - ...
> all of this did not bring any improvements.
> When I click or type idlde.exe I get the startup logo for about a tenth of a second on the screen and then it goes away and nothing happens. No sign of any process anywhere.
> Below is the error reported in one of the first of my .log files. I googled this error and found it in the forum bugs.eclipse.org under comment nr. 19:https://bugs.eclipse.org/bugs/show_bug.cgi?id=234661
>
> I'm working with IDL 8.1 on a 64 bit window 7 pro laptop.
> If anybody has a suggestion that might help, it would be very much appreciated.
> Please notice that I would really hate the idea of having to reinstall the whole system... The level of frustration is REALLY high. The last attempted solution proposed from Exelis dates back to the 28 of March.
>
> Thanks,
> Helder
>
> **** .log file error ****
> !ENTRY org.eclipse.ui 4 0 2012-03-12 16:51:32.027
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalStateException)
>     at org.eclipse.swt.SWT.error(SWT.java:3884)
>     at org.eclipse.swt.SWT.error(SWT.java:3799)
>     at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:137­)
>     at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3885)
>     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3506)
>     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2405)
>     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
>     at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
>     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(Work bench.java:493)
>     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
>     at org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication­.java:113)
>     at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java­:194)
>     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication­(EclipseAppLauncher.java:110)
>     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseA­ppLauncher.java:79)
>     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368­)
>     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.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)
> Caused by: java.lang.IllegalStateException
>     at org.eclipse.jface.text.projection.ProjectionMapping.toImageL ine(ProjectionM­apping.java:480)
>     at org.eclipse.jface.text.TextViewer.modelLine2WidgetLine(TextV iewer.java:5237­)
>     at org.eclipse.jface.text.JFaceTextUtil.modelLineToWidgetLine(J FaceTextUtil.ja­va:224)
>     at org.eclipse.jface.internal.text.source.DiffPainter.paintLine (DiffPainter.ja­va:220)
>     at org.eclipse.jface.internal.text.source.DiffPainter.paint(Dif fPainter.java:1­58)
>     at org.eclipse.jface.text.source.LineNumberChangeRulerColumn.do Paint(LineNumbe­rChangeRulerColumn.java:190)
>     at org.eclipse.jface.text.source.LineNumberRulerColumn.doubleBu fferPaint(LineN­umberRulerColumn.java:692)
>     at org.eclipse.jface.text.source.LineNumberRulerColumn.redraw(L ineNumberRulerC­olumn.java:844)
>     at org.eclipse.jface.internal.text.source.DiffPainter.redraw(Di ffPainter.java:­382)
>     at org.eclipse.jface.internal.text.source.DiffPainter.access$2( DiffPainter.jav­a:381)
>     at org.eclipse.jface.internal.text.source.DiffPainter$2.run(Dif fPainter.java:3­71)
>     at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>     at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:134­)
>     ... 22 more
>
>

Did you apply this patch (Article ID: 4672 on Exelis page) ?
"Patch available for IDL 8.1 Workbench crash problem caused by GDI
object / handle leak "
alx.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Can't launch IDL DE anymore...
Next Topic: What does GRID keyword to INTERPOLATE do?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 06:28:34 PDT 2025

Total time taken to generate the page: 1.04213 seconds