Memory leak? Error creating dialog...

General Macro Scheduler discussion

Moderators: JRL, Dorian (MJT support)

Post Reply
Snickers
Macro Veteran
Posts: 151
Joined: Thu Dec 09, 2004 3:01 pm
Location: Somewhere in TX

Memory leak? Error creating dialog...

Post by Snickers » Fri Aug 17, 2007 2:57 pm

I have been writing a script for close to 2 weeks 12 - 18 hours per day. I have not restarted my computer until about 5 minutes ago. During the process of writing and testing this script, there has been only one dialog that shows everytime I test it. It is the Login dialog. Last night, for the first time, I received an error when starting my script. It said, "Error creating dialog Login"

To no avail, I added some waits thinking that maybe it was processing to fast. This morning the problem still existed. Since this dialog had been created at least 1000 times without a computer restart, I thought that maybe there was some kind of memory leak or something else far above my head.

After a restart the problem went away.

Even though there is no problem currently, is there any reason you can think of that the dialog started having problems? And is there a way to prevent it?

User avatar
JRL
Automation Wizard
Posts: 3529
Joined: Mon Jan 10, 2005 6:22 pm
Location: Iowa

Post by JRL » Fri Aug 17, 2007 3:24 pm

Occasionally, if a script crashes, it will appear to be closed but Macro Scheduler will still be processing it. You can edit the script and you might even be able to run it again unless it creates a dialog. If a dialog was creaated, Macro Scheduler will still have that particular dialog active and won't let you define it again.

Shutting down Macro Scheduler would have resolved the problem. by shutting down your computer you also resolved the problem.

Marcus can probably provide a more detailed explanation if you need it.

Snickers
Macro Veteran
Posts: 151
Joined: Thu Dec 09, 2004 3:01 pm
Location: Somewhere in TX

Post by Snickers » Fri Aug 17, 2007 3:32 pm

JRL wrote:Occasionally, if a script crashes,...
The script did crash. It displayed an error message when I had an "incorrect parameter". This is more than likely the cause of the error then.

Thank you for the explanation.

Post Reply
cron
Sign up to our newsletter for free automation tips, tricks & discounts