X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 07 Feb 2014 11:51 AM by  anon
IDLDE 8.3 burns CPU
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
07 Feb 2014 11:51 AM
    We've just installed IDL 8.3.0 and I'm starting to use IDLDE with linux RHEL6 x86_64. Simply opening IDLDE, not running any commands at all, causes 1 full core of my quad-core hyperthreaded Dell Latitude to run at 100% continuously. The fan goes on and keeps running until I exit IDLDE. This didn't happen with IDL 8.2. Is there a setting that would help? Any idea what it's working so hard at? Diagnostics I can check? Thanks, Kim

    Deleted User



    New Member


    Posts:
    New Member


    --
    07 Feb 2014 12:23 PM
    I have listed a couple of suggestions below: 1) Could you please try starting "idlde" using the "-outofprocess" switch and see if that helps. This essentially separates the IDL process from workbench (eclipse) process. For example: idlde -outofprocess 2) Do you have a lot of projects in your workspace? If you do try closing all none essential projects and see if that helps with he problem?

    Deleted User



    New Member


    Posts:
    New Member


    --
    07 Feb 2014 01:03 PM
    Thanks for the quick reply. The -outofprocess flag seems to solve the issue. I haven't run a lot of code yet, but I've successfully executed some common commands I use. Is there any disadvantage of using this option? I have 8 projects open, but each one has dozens or hundreds of files. It would be inconvenient to close many of them. Kim

    Deleted User



    New Member


    Posts:
    New Member


    --
    12 Feb 2014 02:22 PM
    There are a couple of side affects of using "-outofprocess" that I know about: 1) The graphic windows generated using IDL 8 Graphics (such as plot(),window(),surface(),etc) might not look as good. However, (in my opinion) the "-outofprocess" windows are more functional. 2) Since IDL 8.2, the graphics windows will by default show up above the workbench. If you use "-outofprocess", this will not work because the window order will just be controlled by the operating system.
    You are not authorized to post a reply.