msched.exe has stopped working (memory leak?)

headgeek · Post by **headgeek** » Mon Jan 08, 2018 7:10 pm

I have several computers using MacroScheduler without issue. All scripts include, at one time or another, to run an iMacros script to capture information from a website. All PCs are working without any MacroScheduler issues, except for one.

At random intervals, at the end of the script, MacroScheduler will crash and give me a message of "msched.exe has stopped working". At one point, I was running several imacros at the same time & MacroScheduler seemed to crash more often, so I changed it to run them one at a time, and now it seems to be better... but still causes crashes. Any ideas? I can't share my code.

Specs:
Macro Scheduler 14.4.03 October 2017
Windows 10 Pro - Version 1709, OS Build 16299.192
Intel Xeon 16GB ram

OS Error report:
Source
msched.exe

Summary
Stopped working

Date
‎1/‎8/‎2018 1:54 PM

Status
Report sent

Description
Faulting Application Path: C:\Program Files (x86)\Macro Scheduler 14\msched.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: msched.exe
Application Version: 1.0.0.0
Application Timestamp: 59f8b24c
Fault Module Name: combase.dll
Fault Module Version: 10.0.16299.15
Fault Module Timestamp: 811a4962
Exception Code: c0000602
Exception Offset: 000faeda
OS Version: 10.0.16299.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 64aa
Additional Information 2: 64aa35b012aadee5ea60951d39d8398d
Additional Information 3: 85c0
Additional Information 4: 85c02d0cb0f43ce6b34359277fe68ce3

Extra information about the problem
Bucket ID: 3a560d4e468b302c9a8e41ae44af190f (1913539108411480335)

Post by **Marcus Tettmar** » Tue Jan 09, 2018 9:56 am

The crash is in combase.dll which I suspect has something to do with COM. You mention you are doing something with iMacros. I guess therefore you may be using their COM object from VBScript? Are you always freeing the object properly?

headgeek · Post by **headgeek** » Wed Jan 10, 2018 7:16 pm

Thank you for the reply. I'm using just the standard iMacros language. Does this include VBscript (as I thought that only was used to make multiple macros work together.)

It's just weird that the crashes happen upon Macro Scheduler closing.

If you're sure that this isn't an issue with macroscheduler, I will send this over to iMacros to look into.

Post by **Marcus Tettmar** » Mon Jan 15, 2018 5:27 pm

Not sure how you can be running iMacros code from within Macro Scheduler?

msched.exe has stopped working (memory leak?)

msched.exe has stopped working (memory leak?)

Re: msched.exe has stopped working (memory leak?)

Re: msched.exe has stopped working (memory leak?)

Re: msched.exe has stopped working (memory leak?)