msched.exe memory keeps growing

[MikeSr]

Trying to understand why the memory usage keeps growing in the example below.
Note:
"MainTest" script is running and not calling the "MarcoTwo" script memory growth is nominal.
If "MainTest" is calling "MacroTwo" then the memory usage grows!
I built this quick test program to try to figure out why my actual program that I have been wrighting has been gradually slowing down as the hours pass.

"MainTest"
//*******************************
//** TEST LOOP MAIN MACRO *****
//*******************************
Let>VAREXPLICIT=0


Let>w=1
Label>Startit
If>w=100
goto Endit
Wait>0.01
Else
Let>w=w+1
Message>%w%
Wait>.01
Goto Startit
Endif

Label>Endit
Message>Calling Macro Two!
Wait>0.5
Macro>C:\Users\Mikesr\Documents\Macro Scheduler 11\MacroTwo.scp
Let>w=1
Goto>Startit

"MacroTwo"
//*******************************
//**** Macro Two *****
//*******************************

Message>Got To Macro Two !!

Not sure if I am missing somthing here.

Kind Regards

[gdyvig]

Hi MikeSR,

I tried running your script under WindowsXP, both from the script editor and by doubleclicking MainTest.scp in Windows Explorer.

I did not see any increase in memory usage either for msched.exe or for the system overall.

Is either MainTest.scp or Macro.scp doing something besides what you posted?


Gale

[MikeSr]

Did you create two seperate macros?
Macro 1 "MainTest"
Macro 2 "MacroTwo"

Macro 1 is calling Macro 2

Running just Macro 1 and commenting out the Call to Macro 2 allows the memory to remain the same.
Running it as I mentioned causes the memory to increase by 2K per program scan.

I monitor the memory usage from Windows Task Manager / Processes.
I am running Vista.

Let me know

[gdyvig]

Yes, 2 separate macros.
Macro1 calls Macro2.
I also monitored from Windows Task Manager / Processes.
I checked for msched.exe.
Also looked to see if any other processes were growing.
msched.exe held steady.
Some other processes went up and down but did not seem to be growing long term.


Gale

[MikeSr]

I ran the test programs on two differant Vista Machines.
Both yield the same result. msched.exe memory is growing.
Are you using a Vista operating system?

[gdyvig]

We are trailing edge around here.
Using Windows XP SP3.

Anyone out there with Vista who can try out Mike's script?


Gale

[MikeSr]

I installed on a XP Pro machine that I have. It initially show some memory fluxuation, but then settled down and stayed relatively steady.Some jumps occationally but then it would return to the previous memory usage value.

So..... this looks like a Vista issue!!! What a suprise !!!.

Hope Marcus can take a look at this.

[matthiasR]

Hi,

i have run your scripts now for about 10 minutes under Windows Vista Ultimate. I cannot see any growing memory usage.

Regards,

Matthias

[Marcus Tettmar]

We were able to trace this issue to a memory leak which has now been fixed in 11.1.20.

[jpuziano]

We were able to trace this issue to a memory leak which has now been fixed in 11.1.20.

Great, thanks Marcus. And thank you very much MikeSr for taking the time to post this issue.

Memory leaks are evil as they threaten the stability of any macro that must stay running a long time. With this found and fixed, you have helped to improve Macro Scheduler and have benefited us all.

Here's 10 reputation points in appreciation - I hope you win a T-shirt in the next go-round, I think you've earned it.

Some folks here might think that reputation points are only for rewarding someone who has helped you solve a problem.

I think that in addition, folks who report bugs that get fixed... also deserve recognition and thanks.

What do the rest of you think? If you agree, why not show your support by throwing a few more points MikeSr's way.

Who knows, it might encourage others to report bugs they have been "living with" and if they too get fixed, things just get better for us all.

I don't see a down side there.