Unfortunately I have also experienced the memory leak in RDi V9.0. Not as severe as RDP V8.5 though; nothing where it was maxed out. But from just 15 minutes of usage I have seen it creep up past 500K, 600K or so and it started around 100K. Some increase is expected, but when you're working with the LPEX Editor or the Search function and that's about all I was doing, I don't think it would explode that much. Sounds like there is still some leakage problems going on.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Anderson, Kurt
Sent: August 02, 2013 10:26 AM
To: 'Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (wdsci-l@xxxxxxxxxxxx)'
Subject: [WDSCI-L] RDi 9.0 Memory Leak
I had my IDE become nearly unresponsive yesterday so I turned on the heap allocation display and saw it was maxed at ~1024.
Has anyone experienced a memory leak in 9.0? Has it been reported?
I haven't had it happen since, but am keeping an eye on my heap allocation now.
Kurt Anderson
Sr. Programmer/Analyst at CustomCall Data Systems
[Description: Description: Description: cid:image001.jpg@01CD0CDD.2AC4AAD0]
phone: +1 608 274 3009
web: www.customcall.com<
http://www.customcall.com/> | email: kanderson@xxxxxxxxxxxx<mailto:kanderson@xxxxxxxxxxxx>
A Division of Enghouse Systems Ltd.<
http://www.enghouse.com/> (TSX:ESL)
This e-mail and attachment(s) may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this message is strictly prohibited. If received in error, please notify the sender immediately and delete/destroy the message and any copies thereof. Although Associated Banc-Corp and/or its affiliates (collectively "Associated") attempt to prevent the passage of viruses via e-mail and attachments thereto, Associated does not guarantee that either are virus-free, and accepts no liability for any damage sustained as a result of any such viruses. Any federal tax advice contained in this communication (including any attachments) is not intended or written to be used or referred to in the promoting, marketing, or recommending of any entity, investment plan or agreement, nor is such advice intended or written to be used, and cannot be used, by a taxpayer for the purpose of avoiding penalties under the Internal Revenue Tax Code
midrange.com
