Push2Run Application Force Closes (Presumably)

[sj1765]

Hi,

What a great program this is. Have got it successfully working using Pushover. Originally had it working using Dropbox, but found this would intermittently stop working creating command.txt(1), command.txt(2) etc.

Anyway, using Pushover is great thus far, however, sometimes I will come back to my PC (running Windows 10 Professional 10.0.18363 Build 18363) and the app has disappeared from the system tray, presumably it has force closed for some reason, meaning that commands aren't received.

Do you know why this might be happening?

Thanks again. It's a brilliant program!

Scott

[RobLatour]

Thanks, glad you like the program.

I put a change in the last version of the program to deal with the dropbox issue you describe below; also if you want to go back to using it you should make a minor change to your IFTTT applet, as described in the revised instruction - step 14 - here: https://push2run.com/setup_dropbox.html Basically, the new part is:

the Content field:
should contain:
the Device name you used in step 3 above. It should be followed by "<br>" without the quotes as shown below,
followed by the IFTTT ingredient {{TextField}} and by "<br>" without the quotes as shown below,
followed by the IFTTT ingredient {{CreatedAt}} and by "<br>" without the quotes as shown below.

with the part in bold having change.

regarding the program disappearing from the systray, can you be a little more specific? When you say the systray, do you mean the area just to the left of the system clock at the bottom right of your screen? If yes, is it possibly just being grouped in with the other icons which you can see if you click on the up pointer ( ^ ) to the left of the system clock - or do you mean the program stops running altogether?

[sj1765]

Hi Rob,

Thanks for that. Have done the change for Dropbox in case I go back to using it (though Pushover seems to be great and maybe faster(?))

In regard to the icon disappearing from the systray, I do mean the area to the left of the clock. The 'show hidden icons' button shows it also isn't there so the application has entirely closed for some reason.

In fact, I just went to check now; ithe icom was there so I hovered over it with my cursor and it automatically disappeared (closed). I restarted the application, it's now in the hidden icons area again, I hover over it and it's fine...

[RobLatour]

Well, that should not happen.

Please go to the Push2Run options window, and under 'session log' please check the option to write to disk.

Next time this happens, you'll need to restart the program again, but please go back to that same options window and click on the session log file name and it will open up the folder in which it is stored. After that, you can look for a clue in the log that might indicate why it was shut down the last time around. If you want to post your log here, I can take a look.

[sj1765]

Thank you! Will do.

[sj1765]

So, it just happened again. Here's the session log from today (25th May):


2020-05-24 14:04:53.866 - Incoming Pushover push ...
2020-05-24 14:04:53.866 - open J
2020-05-24 14:04:54.475 - action completed

2020-05-24 14:05:45.370 - Incoming Pushover push ...
2020-05-24 14:05:45.370 - open S
2020-05-24 14:05:45.964 - action completed

2020-05-25 20:39:51.053 - Push2Run version 3.0.3.0 started

2020-05-25 20:39:51.103 - Windows UAC notify feature is on

2020-05-25 20:39:51.108 - Normal privileges are in effect

2020-05-25 20:39:51.785 - Current network adapter is Wi-Fi

2020-05-25 20:39:52.091 - Network status is up

2020-05-25 20:39:56.800 - Connection with Pushover established

2020-05-25 20:39:58.573 - Obsolete Pushover notifications for Push2Run_SCOTT-DESKTOP have been dismissed

2020-05-25 20:39:58.737 - Dropbox monitoring begun for D:\Dropbox\Apps\Push2Run\



Seems strange that Push2Run started at 20:39:51 seeing as the computer has been on since the 24th and hasn't shut down or restarted as far as I'm aware.

[RobLatour]

well, whatever caused you version of Push2Run to restart, at least now we know in what timeframe it happened.

Unfortunately, there's no other clues in the log.

Having that said, Windows itself has an event log which might yield some additional information

do you know how to use this? If not, here is a quick link that shows you some basics:
https://www.howtogeek.com/123646/htg-ex ... an-use-it/

In short, just looking for something that may have caused your computer to exit Push2Run sometime between 2:04 pm and 8:39 pm.

[sj1765]

Thanks, Rob. I've taken a look but can't pinpoint anything. I've attached the event log for that time period here if you're able to see something I can't?

https://drive.google.com/open?id=17Jwmb ... MhqBBoQR1r

[RobLatour]

According to your log, there were a few things of note:

1. your system went to sleep at 6:11:54 pm and woke up a second later

2. it then directly after in your log there was a sudden time change of over 2 hours
<Data Name="NewTime">2020-04-25T00:36:31.500000000Z</Data>
<Data Name="OldTime">2020-04-24T22:11:55.410477400Z</Data>
which was recorded at 8:36:31 pm

I suspect that means your PC was asleep from 6:11:54 to 8:36:31

However, after that, there was a bunch of complaining in your log about the structure of your C: drive and corruption, and your PC repairing it, right up until about the time that Push2Run seems to have been restarted (based on the timing shown in your Push2Run log).

So in short, it appears when your PC goes into sleep mode, not coming out of it very gracefully.

Accordingly, unless you manually put your PC to sleep, you might want to go into your Windows 'Power and Sleep' settings, and switch the period of time after which your PC goes to sleep to be 'Never'.

It's just a guess, but if you try it, please let me know if it helps.

Rob

[sj1765]

Thanks. Very strange as it's already set to 'Never'. I went into advanced setting and found a setting called 'Hybrid Sleep' that was set to on, so I've turned that off and I guess see if it changes anything...!