OI 7.21 Memory Issues (OpenInsight 32-Bit)
At 23 JUN 2006 12:59:19PM Rajee Setty wrote:
Errors encountered when running OI 7.21/OIPI reports with certain data.
1. Errors are inconsistent, they are generated anywhere from 1 - 8 runs at the server level.
2. If the OI 7.21 program set is installed on a local workstation, it is harder to create the errors i.e. takes several runs to generate the errors.
3. This is happening only in OI7.21, same code works fine with OI 7.11.
Why does OI 7.21 generate these memeory errors and not OI 7.11 even if there is a memory leak in the system?
Also, OI 7.21 seems to be more client dependent as the errors can be easily duplicated when run on the server versus the local workstation.
At 23 JUN 2006 01:01PM John Bouley wrote:
What errors?
At 23 JUN 2006 01:03PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
There are a very finite amount of memory leaks in OI 7.2.1 so you have to be doing very specific things to experience them. Frequently identifying the problem area and coding around the issue provides an interim solution to the problem.
World leaders in all things RevSoft
At 24 JUN 2006 02:34PM Jim Vaughan wrote:
]] There are a very finite amount of memory leaks in OI 7.2.1 «
…just out of interest, what code would cuase these leaks?
At 25 JUN 2006 06:44AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
The most obvious one is if you change fonts a lot on a window, toggling between bold and normal for example. (Props to a UK client for tracking this one down).
World leaders in all things RevSoft
At 26 JUN 2006 05:23PM Karen Oland wrote:
Calling MAPISendMail several times (and canceling the Send) seems to send it into hysterics as well. But, it looks like the problem is in outlook, not solely OI.
At 27 JUN 2006 09:33AM Bob Carten wrote:
Hi Rajee
What is the error you get?
Do you get a message box with a round red X and the message "Out of Memory"?
Bob
At 27 JUN 2006 10:23AM Sean FitzSimons wrote:
Rajee,
I have the information necessary to track this down. Once I have an answer I'll contact you. Thank you.
Sean
At 27 JUL 2006 05:12PM Sean FitzSimons wrote:
Rajee,
I am still tracking this one down. I am recreating the error. It is in the NTDLL.DLL. This has led me donw the DEP path, so at the moment I am searching for further details regarding DEP and software.
Sean