A Viewer for Windows, Cast, NotifyOnDemand, Push2Run and SetVol

Hi all.

Been using Push2Run to automate a handful of PC tasks (mainly shutdown/sleep). All has been well until the last update, now the app randomly closes every day, usually without receiving any commands.

Windows logs - both events occurring at the same time:

Source: Application Error

Faulting application name: Push2Run.exe, version: 3.2.0.0, time stamp: 0x5f83737e
Faulting module name: KERNELBASE.dll, version: 10.0.18362.1139, time stamp: 0x6a8e6b97
Exception code: 0xe0434352
Fault offset: 0x00114662
Faulting process id: 0xba4
Faulting application start time: 0x01d6abee1383404e
Faulting application path: C:\Program Files\Push2Run\Push2Run.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 33b087af-0471-4b15-b8a5-a5bec51fea6d
Faulting package full name:
Faulting package-relative application ID:


Source: .NET Runtime

Application: Push2Run.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
at System.Drawing.Bitmap..ctor(Int32, Int32, System.Drawing.Imaging.PixelFormat)
at System.Drawing.Bitmap..ctor(Int32, Int32)
at System.Drawing.Icon.BmpFrame()
at System.Drawing.Icon.ToBitmap()
at System.Windows.Forms.ThreadExceptionDialog..ctor(System.Exception)
at System.Windows.Forms.Application+ThreadContext.OnThreadException(System.Exception)
at System.Windows.Forms.Timer+TimerNativeWindow.OnThreadException(System.Exception)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at #=zpdXniX1hNU2e9bQfQg==.Main()

Any idea what's going on here? Cheers.

Interestingly, I haven't seen this myself, and I'm not sure what is going on here.

Changes in 3.2 were restricted to import and export functionality.

You may want to try and download and install version 3.3 (released last week) to see if you're getting the same issue.

Also, you may want to reload Microsoft's dot net framework (Push2Run requires version 4.6.2)
https://support.microsoft.com/en-ca/hel ... or-windows

Thanks.

I looked for the previous version as an easy fix, but couldn't find a link on the website, I'll have another look.

I checked my .NET, it's 4.8 (current). The process for reinstalling it seems convoluted, so I'll try it if the rollback doesn't work.

PS: Just realised I posted this in the wrong section, sorry

As an update.

I updated to the new version (3.3), the issue persisted. I looked into reinstalling .Net, it's a nightmare on W10. So I looked into the error code and what throws it. Discovered it can be related to memory, so I cleaned up my system (removed some automation I can live without, sorted out some leaks, etc).

Haven't experienced any crashes since. Seems it was a memory problem.

Thanks for posting an update GTrainAU.

I assume the changes you made, other than upgrading to the most recent version of Push2Run, were specific to your system. Having that said, were there any in particular that you would see as being important for others to know about - or do you feel the issues you were having were somehow tied to your machine in particular?

Thanks again, hope the program is of good use to you.

No, I think my system is simply lacking in available memory, given my intended use.

Only recommendation is that if people run into similar issues, try to free up some memory and see if that helps.