someone else encountered the following problem with RDp 8.5.1
When working with RDp, memory get allocated and never freed, i.e. within 30 minutes of work (simply coding, nothing else) arround 1 GB of memory is allocated, everything slows down, it takes a few seconds to get a simple character inserted. Simply typing eats almost all CPU.
If I end RDp it takes an amount of time until memory is freed and I can restart RDp. At the beginning everyhting works ok, but within 30 minutes same situation as before.
Could it be the automatic outline refresh causes this problems?
If so is there a way to prevent the outline from being refreshed automatically.
I now reset to RDp 8.0.3 which works without problems.
This topic has been locked.
3 replies Latest Post - 2013-02-08T06:42:23Z by B.Hauser
Pinned topic RDp 8.5.1 - Allocates Memory and eats all CPY
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-08T06:42:23Z at 2013-02-08T06:42:23Z by B.Hauser
eric.simpson 0600014623103 PostsACCEPTED ANSWER
Re: RDp 8.5.1 - Allocates Memory and eats all CPY2013-02-06T13:15:52Z in response to B.HauserWe are investigating the issue.
You can turn off the automatic refresh of the ILE RPG Outline view in the preferences.
Look on the Remote Systems>Remote Systems LPEX Editor>IBM i Parsers>ILE RPG preference page for the 'Update the Outline view when text is changed in the editor' preference.
B.Hauser 1000007U1D10 PostsACCEPTED ANSWER
Re: RDp 8.5.1 - Allocates Memory and eats all CPY2013-02-08T06:42:23Z in response to eric.simpson@Eric,
Hmmmmmm, Sorry I couldn't find this option (eventhough I checked all the preferences)!
Interesting discussion, even though it did not cover my problem.
But I think I need to follow this list more often.
JonParis 1200007C6K33 PostsACCEPTED ANSWER
Re: RDp 8.5.1 - Allocates Memory and eats all CPY2013-02-06T16:11:11Z in response to B.HauserThere has been extensive discussion on this on the WDSC-L list at Midrange.com the main thread starts here: http://archive.midrange.com/wdsci-l/201301/msg00005.html
The post I found most useful is this one from one of the developers which shows how to activate the heap monitor. If memory consumption starts to go haywire this lets you force garbage collection by pressing the garbage can icon. Details here: http://archive.midrange.com/wdsci-l/201301/msg00064.html