Problems with IDL 8.1: the Development Enviroment is not starting [message #79853] |
Thu, 19 April 2012 08:05  |
Helder Marchetto
Messages: 520 Registered: November 2011
|
Senior Member |
|
|
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(EclipseAppLauncher.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(ProjectionMapping.java:480)
at org.eclipse.jface.text.TextViewer.modelLine2WidgetLine(TextV iewer.java:5237)
at org.eclipse.jface.text.JFaceTextUtil.modelLineToWidgetLine(J FaceTextUtil.java:224)
at org.eclipse.jface.internal.text.source.DiffPainter.paintLine (DiffPainter.java:220)
at org.eclipse.jface.internal.text.source.DiffPainter.paint(Dif fPainter.java:158)
at org.eclipse.jface.text.source.LineNumberChangeRulerColumn.do Paint(LineNumberChangeRulerColumn.java:190)
at org.eclipse.jface.text.source.LineNumberRulerColumn.doubleBu fferPaint(LineNumberRulerColumn.java:692)
at org.eclipse.jface.text.source.LineNumberRulerColumn.redraw(L ineNumberRulerColumn.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.java:381)
at org.eclipse.jface.internal.text.source.DiffPainter$2.run(Dif fPainter.java:371)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:134)
... 22 more
|
|
|
|
|
Re: Problems with IDL 8.1: the Development Enviroment is not starting [message #79991 is a reply to message #79853] |
Thu, 19 April 2012 09:21   |
Helder Marchetto
Messages: 520 Registered: November 2011
|
Senior Member |
|
|
On Thursday, April 19, 2012 6:11:28 PM UTC+2, David Fanning wrote:
> Helder writes:
>
>> it was worth a try. I did set this preference in the command line. There was no visible improvement. I also checked afterwards with pref_get that I did indeed set this variable to 1.
>
> I know you don't want to hear this, but I would
> do a complete fresh install after clearing
> out ALL my IDL directories (including the
> invisible ones!). Did you install the 64-bit
> version of IDL? That's what I am using. I note
> that I had a similar problem, and that it was caused
> by a function that I had left over in a directory from
> a previous beta version of the software.
>
> Don't know what to tell you. This is just one of
> many frustrations I've had with IDL 8 in general. :-)
>
> Are you updating your JAVA version on a regular basis.
> Eclipse problems could be related to JAVA. I update
> my machines regularly.
>
> I feel for you. Python, by the way, has its own problems.
> Maybe there is no really good solution anymore.
Thanks David for your answers/comprehension. I just noticed that I can start DE of IDL 32-bit, but not IDL 64-bit... Strange... I would have thought that the crash was caused by the DE... I don't see how this relates to the 32 or 64 version.
I'll contact Exelis once again.
Cheers,
Helder
|
|
|
|
|
Re: Problems with IDL 8.1: the Development Enviroment is not starting [message #79994 is a reply to message #79853] |
Thu, 19 April 2012 08:56   |
Helder Marchetto
Messages: 520 Registered: November 2011
|
Senior Member |
|
|
On Thursday, April 19, 2012 5:36:35 PM UTC+2, David Fanning wrote:
> Helder writes:
>
>> I would try that, but unfortunately I can't access the properties tab... Is this parameter to be found in a (accessible) file?
>
> The preferences are stored in the "idl.pref" file in
> your APP_USER_DIR, wherever the hell that is! The
> preference you are looking for is IDL_GR_WIN_RENDERER.
>
> (My APP_USER_DIR appears to be something like /Users/David/.idl)
>
> Perhaps you can start IDL up in command line mode (rather than
> use the Workbench) and set this preference with PREF_SET.
> Then switch back to Workbench mode.
>
> PREF_SET 'IDL_GR_WIN_RENDERER', 1, /COMMIT
Thanks David,
it was worth a try. I did set this preference in the command line. There was no visible improvement. I also checked afterwards with pref_get that I did indeed set this variable to 1.
Cheers,
Helder
|
|
|
|
|
|
|
Re: Problems with IDL 8.1: the Development Enviroment is not starting [message #79999 is a reply to message #79853] |
Thu, 19 April 2012 08:18   |
Helder Marchetto
Messages: 520 Registered: November 2011
|
Senior Member |
|
|
Even more frustrating, but thanks.
Actually my problems started when I testing the graphics using the following (harmless) code:
PRO ex_widget_window_event, event
IF TAG_NAMES(event, /STRUCTURE_NAME) EQ 'WIDGET_KILL_REQUEST' THEN BEGIN
WIDGET_CONTROL, event.top, /DESTROY
ok = dialog_message('Plot window closed', /INFORMATION)
ENDIF
END
PRO ex_widget_window
wBase = WIDGET_BASE(/COLUMN, TITLE='Plot', /TLB_KILL_REQUEST_EVENTS)
wDraw = WIDGET_WINDOW(wBase, X_SCROLL_SIZE=400, Y_SCROLL_SIZE=400)
WIDGET_CONTROL, wBase, /REALIZE
WIDGET_CONTROL, wDraw, GET_VALUE=oWin
oWin.Select
p = PLOT(/TEST, /CURRENT, /FILL_BACKGROUND)
XMANAGER, 'ex_widget_window', wBase
END
Do you see any reason why this would cause major crashes?
Thanks,
Helder
On Thursday, April 19, 2012 5:13:50 PM UTC+2, David Fanning wrote:
> Helder writes:
>
>> 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
>
> I don't have any suggestions, except to tell you
> I have IDL 8.1 on an identical 64-bit Windows 7 Pro
> laptop and it works great. The function graphics are
> especially easy to use. ;-)
>
> Cheers,
>
> David
>
>
>
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
|
|
|
|
Re: Problems with IDL 8.1: the Development Enviroment is not starting [message #80050 is a reply to message #79853] |
Mon, 23 April 2012 13:55   |
Helder Marchetto
Messages: 520 Registered: November 2011
|
Senior Member |
|
|
On Monday, April 23, 2012 10:45:11 PM UTC+2, Scott E wrote:
> Based on the stack trace, it looks like you are starting up a workspace with a Diff view in it that for some reason has corrupted mementos. Have you tried starting with a new, clean workspace? You can do this by passing the -data parameter, E.g.
>
> idlde.exe -clean -data c:\myfolder\myworkspace
>
> where c:\myfolder\myworkspace is a new empty directory you created.
>
> Hope that helps.
>
> Cheers,
> Scott
Dear Scott,
I've tried erasing completely my workspace and I've tried doing a clean start on a new workspace. Both didn't work :-(((
Thanks again.
Cheers,
Helder
|
|
|
|
Re: Problems with IDL 8.1: the Development Enviroment is not starting [message #81353 is a reply to message #80051] |
Wed, 12 September 2012 05:56  |
kidpix
Messages: 23 Registered: July 2007
|
Junior Member |
|
|
Hi,
I didn't want to loose all my personalization, so I traced back where the Diff view is called in the idlde startup. It was in the file:
/Users/[my_user]/IDLWorkspace81/.metadata/.plugins/org.eclip se.ui.workbench/workbench.xml
precisely, I erased the lines (it depends on the organization of your workbench):
<view id="org.eclipse.help.ui.HelpView" partName="Help">
<viewState BrowserPart.url=" /org.eclipse.team.svn.help/gettingStarted/subversion/svn_dif fs.html " pageId="browser-page"/>
</view>
Than it started as normal, warning that one file was modified out on the SVN control, a re-sync to my repository and all back to normal.
Cheers!
PS: It was my fault, I modified a file remotely using vim!
On Monday, April 23, 2012 10:45:11 PM UTC+2, Scott E wrote:
> Based on the stack trace, it looks like you are starting up a workspace with a Diff view in it that for some reason has corrupted mementos. Have you tried starting with a new, clean workspace? You can do this by passing the -data parameter, E.g.
|
|
|