Buck,
In regards to you suggestions:
1) Find out what it is about your environment that's killing RDi --> WISH I COULD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2) Stop using RDi
You left out choice "3.)" Create new workspace, when I get the "Non Responding", a.k.a. "Milky-White-Screen-Of-Death". <LOL>
I guess I will see how that works for me! At least I can import the key-settings & RSE UI. The other settings I have to do manually.
I will start the count down, to see how long it takes until I get the "Non Responding" again... <Evil Smirk>
Whatever works...
I prefer option 4.) IBM fixes RDI so that NO ONE gets the "Not Responding" memory leak.
PS. Once in a while I get the "Milky-White-Screen" on Microsoft products. But, I just wait a few seconds, and it catches up! I have let RDI wait 1-hour or more, and it still does not catch up like Microsoft products. <Just saying>
RDI is the ONLY SOFTWARE that locks up on me. It is the most used software on my PC. <smirk>
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Thursday, October 29, 2015 12:34 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDi 9.5 "not responding"
On 10/29/2015 11:22 AM, Ken Killian wrote:
But, I have gotten the "Not Responding" on EVERY SINGLE release of
RDI... <Puzzled-Look>
And I've seen it maybe once since the OS/2 days. This strongly points to something in your environment, something that you run on your PC that I don't run on mine. And something that the lab doesn't run on theirs.
That's no consolation: clearly you need to run RDi at work, so what can you do? If I were faced with this problem, I'd almost certainly switch to an editor / IDE that didn't require me to kill it with Task Manager.
The only other real option is to change your environment. Assume your IT people are interested in helping, get a PC / laptop that has a clean install of Windows. No antivirus, no firewall, no groupware integrations, no nothing except the clean install of Windows. Have the IT people allow you to one IP address: the IBM i machine. You only use this PC to edit code, and no one else is using the subnet that you're on. The goal is to make the most absolute vanilla environment that is humanly possible. Now load RDi and start using it.
If, as I suspect, you don't have any issues with RDi going non-responding, you will have proved to yourself and to your company that there's something going on in their environment. But what is it?
Now is where it starts to get time consuming.
Add one thing from the work environment - I'd start with the antivirus - and try it again. Keep adding things from the work environment one at a time until it fails, and when it does, you'll be able to report that the combination of X, and Y, and Z cause RDi to go off the reservation.
That's a lot of work, and it requires the willing assistance from the IT group who maintain your PC and network. But it's becoming clearer every time you post that you face stark choices:
1) Find out what it is about your environment that's killing RDi
2) Stop using RDi
Good luck my friend. If I were in your shoes I'd be using Code/400.
No, it can't syntax check modern code but neither can SEU. And despite being obsolete by a decade, Code/400 is light-years beyond SEU.
--
--buck
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
