When we open forms and run programs, the memory used by Oinsight creeps up all the time.

When the Main Menu is minimised then maximised the memory is flushed.

We tried using garbagecollect and flush to clear unused programs but have not had much luck yet.

This is mainly a problem on a Web Server where we use a timer event to check for emails to be sent and unused engines to be closed.

Anyone has any recommendations on this. The problem is the same on the new beta version.

Thanks

Gerry van Niekerk

Csoft

Is it posted anywhere for download separately?

This behaviour has been seen in Australia at one large site using OI behind a web interface. I sent some VB API code to the bods concerned to assist with automatically (ever 24 hours) minimizing then maximizing the OI32 sessions. (I had done this for other apps, coincidentally).

Talk to David Goddard at Revelation Australia (www.revelationsoftware.com.au) via email and ask about Oryx's OI32 implementation. They may be able to assist.

You can shoot me a mail if you want the API call details I sent there.

I'm certain the necessary calls could be done readily from within OI itself, on a periodic basis.

Steve

Are you using EditTables? We reproduced a memory leak in June of this year which was fixed in Datatbl.dll. There might be an outside chance that this never made it to release.

The Sprezzatura Group

World Leaders in all things RevSoft

Is this a bona-fide problem? It's the first I've heard of anything like this. Memory creep/leaks have always concerned me and it was something we looked for carefully when OI32 first began beta-testing. We were able to help Pat discover a problem when our WM_SETCURSOR trapping was firing WINMSG events in rapid fire. We regularly use TIMER events as well, but perhaps not as persistently as what has been described here.

I'm very interest to understand how minimizing and maximizing a form restores the memory. Is that the only way to get it done? Does this give Revelation enough information to build a real solution in OI 7.0?

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Thanks Steve,

Can you send me your eamil address.

Gerry@csoft.co.nz

Ta

Gerry

Don,

It's real, although I haven't witnessed it first hand, and I suspect it relates to the use of a third party component (note wet finger in the air). I'm tipping SQL / external object thingies and stuff. I think something like a dll isn't destroying itself like I did on red wine tonight…..so we should, er, consume more….no….on second thoughts….where are my tablets?…uh oh…..Nurse???

Sorry Guys I have been away from the office for a few days,

Example

Load OI

Load taskmanager

Do processing in OI

Oinsight memory will increase and increase and increase.

Mainly when using send_message end set_property

The programs we use run on a web server.

What happens now is that oinsight.exe keeps accumulating in memory and the server will eventually bomb out. Depending on the number of transactions this could happen within a few hours.

However if youn minimise and maximise OI the Oinsight memory will reset.

Run OI with the taskmanage open and see the results. We use XP and 2000

However thats not all.

At the bottom of taskmanager it shows the total memory committed, this keeps increasinggggggg and will only reduce when OI is closed, which when running a WEB server you DON'T want to do.

If anyone can't replicate let me know.

Some entry screens when using scripts wont increase the memory by much but when using procedures etc then it becomes a problem.

We tried garbagecollect and flush and this has no effect on total memory used.

Thanks,

Gerry

Csoft

Gerry,

I would very much like to pursue this, but you are going to have to help me. What Don did to help me figure out what was causing his problem was to package up in an RDK a nice little test form from which I was able to replicate his problem. If you could do the same, I promise I will look into it.

Pat

PAT,

Do you want me to email it to you.

I still have your email addressss I think

Gerry

Sure, pat@mcnerthney.com will work.

Pat

View this thread on the Works forum...