Settings file can be corrupted making it impossible to start RIDE

Question

Originally submitted to Google Code by c.martin.taylor on 7 Oct 2009

RIDE has never been particularly quick to launch but it has gotten MUCH WORSE in the past 2 releases. I didn't time it in 0.18 but it was noticeably slower than 0.14 which was the previous version I used.

Now in version 0.19 it was so bad that I did time it. It took 5 minutes to load my (admittedly large and complex) project. During most of this time the CPU on which Python was running on my Dell D620 laptop was fully utilized (see the attached screenshot).

Some of this time may be due to failed attempts by RIDE to import my keyword libraries. Such imports won't work until Issue #256 is fixed, but I can't tell if this is the problem because RIDE doesn't display all the screen output that would normally happen when my libraries get loaded.

Answer 1

Originally submitted to Google Code by c.martin.taylor on 7 Oct 2009

It also takes an excessive amount of time to exit RIDE. For the project that took 5 minutes to open in RIDE it took 1 minute to exit RIDE. This is totally unreasonable and needs to be fixed ASAP.