EventGhost Windows process not ending at exit

[Captain_Tactful]

Hi,
I've found that after couple of days running EG might not close properly, the only reason I need to close it, is to guarantee that changes are saved to the currently running EG system file.
So, I have to open task manager and end process.
Is anyone else experiencing this?
TIA.

[kgschlosser]

this is commonly due to some thread that is not closing properly the thread would be associated to a specific plugin. or it could be the shutdown code in a plugin is malfunctioning and this would cause EG to halt in the middle of shutting down so what i would do is create a new tree. and one at a time add your plugins and test to see if it hangs. once it does report back which plugin is causing the issue.

[Captain_Tactful]

Thanks for the reply.

Another problem that is part of the same issue?
I am unable to save a new system file and open the new system file without a lot of red text appearing.
EG automatically opens a system file from EG version 0.4
I have tried disabling all plugins, but the problems still exist.
My undestanding is by disabling I am immediately stopping the relevant article. Plugin or otherwise.

If I remove plugins do I run the chance of deleting associated macros and actions?

How do I completely remove EG and start from scratch. Uninstalling or installing new version does not help.?

TIA

[Captain_Tactful]

this is commonly due to some thread that is not closing properly the thread would be associated to a specific plugin. or it could be the shutdown code in a plugin is malfunctioning and this would cause EG to halt in the middle of shutting down so what i would do is create a new tree. and one at a time add your plugins and test to see if it hangs. once it does report back which plugin is causing the issue.

Ok, thanks
The Plugin for Velleman K8055D_C is the problem.

[kgschlosser]

the easiest thing to do is to make a new tree and add the plugins you are using one at a time. until the problem shows... this way you are not messing around with your current setup..

if you could also provide me with screen shots of any/all errors. I will check them out for ya. and maybe with a little bit caressing it we can get everything to simmer down and give you an error free EG experience.


Things I need..

what version of EG are you running?
what version of Windows are you running?
screen shots.
debugging log file. to make one of those you will need to run eventghost from a command prompt with -debug following it. this will create a file in %APPDATA%/Roaming/EventGhost folder the file name is log.txt.

[kgschlosser]

I am going to take a look at the Velleman K8055D_C plugin and get it to close all nice nice for ya. so give me about an hour or so and i will see if it is something fairly simple to do.

[kgschlosser]

This should fix the closing issue with the plugin.. it is an egplugin file.. this will automatically install into EventGhost. but it will put the plugin into c:\programdata\eventghost\plugins folder instead of in the installation directory.

if you want to overwrite your existing plugin then change the file extension to zip and open it.. just ignore the info.py file.

it is attached

[Captain_Tactful]

This should fix the closing issue with the plugin.. it is an egplugin file.. this will automatically install into EventGhost. but it will put the plugin into c:\programdata\eventghost\plugins folder instead of in the installation directory.

if you want to overwrite your existing plugin then change the file extension to zip and open it.. just ignore the info.py file.

it is attached

Thank you that's very kind.
Once I had put the latest .dll (v4 from Velleman website) into the EventGhost program files folder with the other .dlls, and renamed it to K8055D_C.dll, the plugin initialised.
Time will tell.
Thanks again.
Now on to the Arduino UNO and 10x DS18B20 and how to handle that.

[kgschlosser]

I am sort of a micro controller fiend. what do you need to know about the Uno?, I have many of them throughout my house all networked and all talking to a central EG. Uno's Mega's and I am soon probably going to replace them all for ESP8266's running MicroPython

[kgschlosser]

and the only thing you need to do to test the plugin is close EG and see if it still gets stuck.. if it doesn't then problem sorted.. if not then i have to leek at something else.. I only breezed through it and there was one thing that jumped out at me so i changed it.

[skribb]

Are you saying the process never ends?

because i have noticed that when i exit EG, surverying the process i can see that it takes an additional 30 seconds for it to die.

[kgschlosser]

Are you saying the process never ends?

because i have noticed that when i exit EG, surverying the process i can see that it takes an additional 30 seconds for it to die.

that is because of a hanging thread. if you run EG in debug mode. and after closing EG open up the log and scroll all the way to the bottom it will tell you what thread was hung. and then we can go from there and see if we can fix it for ya.

K

[skribb]

Are you saying the process never ends?

because i have noticed that when i exit EG, surverying the process i can see that it takes an additional 30 seconds for it to die.

that is because of a hanging thread. if you run EG in debug mode. and after closing EG open up the log and scroll all the way to the bottom it will tell you what thread was hung. and then we can go from there and see if we can fix it for ya.

K

This is the vey bottom of the log:

Code: Select all

2017-03-27 13:48:41  EVENT: Task.Activated.EventGhost
2017-03-27 13:48:51  EVENT: Task.Deactivated.EventGhost
2017-03-27 13:48:51  EVENT: Task.ClosedWindow.EventGhost
2017-03-27 13:48:51  EVENT: Task.Destroyed.EventGhost
2017-03-27 13:48:51  EVENT: Task.Activated.procexp64
2017-03-27 13:48:51  EVENT: Main.OnClose

I can't see any debug specific entries in the log as a matter of fact

[kgschlosser]

run this form the command line

Code: Select all

C:\Program Files (x86)\EventGhost\eventghost.exe -debug

then close EG

then copy and paste this into you windows file explorer

Code: Select all

%APPDATA%\roaming\eventghost

open a file called log.txt
at the bottom of that log file it will tell you what thread is getting stuck

[skribb]

Oh I did not know the debug mode had a separate log file.

This looks interesting¨

Code: Select all

13:54:40: 1 MainThread: Waited for threads shutdown: 5.009387 s
13:54:40: 1 MainThread: The following threads did not terminate:
13:54:40: 1 MainThread:   <Thread(ProcessWatcherThread, started 25860)> ProcessWatcherThread
13:54:40: 1 MainThread: Done!