| Re: IDL 8.0.1 crashes [message #74210] |
Thu, 06 January 2011 08:21  |
lecacheux.alain
Messages: 325
Registered: January 2008
|
Senior Member |
|
|
On 6 jan, 16:55, David Fanning <n...@dfanning.com> wrote:
> vto writes:
>> It looks like most people here use PCs. I'm running
>> IDL on a Mac and it looks like it is slightly more stable.
>> I had IDL 8.0 running for a month, using it daily,
>> before it crashed.
>
> The happy people appear to be running IDL 8 on Linux
> machines. :-)
>
> This goes in karmic cycles. For Windows users this
> is payback for having a decent IDE in the days before
> JAVA, when the Linux crowd had to use that ugly
> monstrosity that turned your editing window into
> grotesque blocks of weird colors.
>
> Probably in IDL 9 the Mac users will be ascendant. :-)
>
> Cheers,
>
> David
>
> P.S. Let's just say if we hang around long enough,
> we will ALL get what we want. ;-)
>
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
I experienced a few crashes by using IDL8 and Windows 7 (both 32 and
64). But no so frequent, maybe one per week in daily utilisation.
always after some using time, with many edit/run/edit cycles.
Sure that IDL8's Workbench is much more fragile than IDL7's one. Maybe
related to the new garbage collector for IDL objects ?
Anyhow, I guess that Eclipse is crashing then, rather than IDL: you
can get some info from java log files (filenames are like
hs_err_pidxxxx.log). Sometimes, the faulting module is "idl.dll", but
you can find others, likely related to error messaging in java.
Not really confortable, since you loose everything from your most
recent IDL work...
alx.
|
|
|
|
| Re: IDL 8.0.1 crashes [message #74212 is a reply to message #74210] |
Thu, 06 January 2011 08:10  |
penteado
Messages: 866
Registered: February 2018
|
Senior Member
Administrator |
|
|
On Jan 6, 1:55 pm, David Fanning <n...@dfanning.com> wrote:
> vto writes:
>> It looks like most people here use PCs. I'm running
>> IDL on a Mac and it looks like it is slightly more stable.
>> I had IDL 8.0 running for a month, using it daily,
>> before it crashed.
>
> The happy people appear to be running IDL 8 on Linux
> machines. :-)
That is payback for the installation, which is easy in Windows, but
frequently troublesome in Linux (and from what others have told me,
also difficult in Macs). Though I have to admit that it has improved a
lot in recent versions (in Fedora, at least).
There are also the issues with the license server, which likes to die
occasionally for no apparent reason. Which is especially troublesome
when the license server is running in some department computer, and
one cannot do anything until the administrator restarts the server
there. The license server also likes to pick fights with the license
servers of other software that use similar systems (such as the PGI
compilers).
|
|
|
|
|
|
| Re: IDL 8.0.1 crashes [message #74215 is a reply to message #74214] |
Thu, 06 January 2011 07:45 |
penteado
Messages: 866
Registered: February 2018
|
Senior Member
Administrator |
|
|
On Jan 6, 1:39 pm, vto <vto...@cfa.harvard.edu> wrote:
> It looks like most people here use PCs. I'm running IDL on a Mac and it looks like it is slightly more stable. I had IDL 8.0 running for a month, using it daily, before it crashed. Crashing means either IDL became totally unresponsive, or just parts quit working (e.g. the editor). In any case, I do not understand some of the concept of the workbench. When IDL crashes (or must be "forced quit"), you loose all the log information. What a concept! You know what you did when it is successful, but you are in the dark when it crashes because you typed the wrong command. Why can't they save the log once a command is issued and before really executing it. Or, at least, give you the option to do so.
Journal files are written occasionally during the session. More
precisely, their output seems to be buffered. So some of the journal
might be saved in a crash.
|
|
|
|
| Re: IDL 8.0.1 crashes [message #74216 is a reply to message #74215] |
Thu, 06 January 2011 07:39 |
vto
Messages: 5
Registered: January 2011
|
Junior Member |
|
|
It looks like most people here use PCs. I'm running IDL on a Mac and it looks like it is slightly more stable. I had IDL 8.0 running for a month, using it daily, before it crashed. Crashing means either IDL became totally unresponsive, or just parts quit working (e.g. the editor). In any case, I do not understand some of the concept of the workbench. When IDL crashes (or must be "forced quit"), you loose all the log information. What a concept! You know what you did when it is successful, but you are in the dark when it crashes because you typed the wrong command. Why can't they save the log once a command is issued and before really executing it. Or, at least, give you the option to do so.
Back to the crashes. Isn't the workbench written in java? I have problems with other java-based programs that they crash eventually. There must be, most likely, some memory problem like accumulating memory leaks or not properly freeing and releasing used memory. Might be good to monitor the memory usage of your machine to see if there is a spike right before IDL crashes.
Volker
|
|
|
|
|
|
|
|
| Re: IDL 8.0.1 crashes [message #74224 is a reply to message #74223] |
Wed, 05 January 2011 18:11 |
penteado
Messages: 866
Registered: February 2018
|
Senior Member
Administrator |
|
|
On Jan 5, 10:08 pm, b_gom <b_...@hotmail.com> wrote:
> Is any one else experiencing random crashes with IDL 8 \ eclipse? IDL dies and disappears about 3 time an hour for me. There is no warning, and I can't find a pattern. Sometimes it happens when the help is open, sometimes not. Sometimes it is when I'm running an object graphics program, sometimes its just when I'm typing into the editor. I get the same behavior on two new windows 7 machines, 64 and 32 bits. I think I was getting similar crashes on XP. All the other software on these systems runs fine. I'm guessing it is eclipse related, but I could be wrong.
>
> If anyone else is seeing this, is there any hope for a solution? I wish ITT had some sort of crash logging so that users could report how their buggy software is dying..
I never noticed such problems, in Vista 64. I have not yet used IDL in
Windows 7, and have not used XP in years.
If I had encountered problems like those, I would try using a
different JVM, and write to ITTVIS support.
|
|
|
|
|
|
|
|
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
