EventGhost

OK so these appcrash messages suck. because they really tell us nothing.
The only way for me to be able to diagnose the appcrash message properly is quite involved. I would have to compile python and every extension module differently. I would have to generate symbol files for each and every one of those extension modules and python as well. then you would have to install Visual Studio 2017 and set it to be used by Windows as the debugger. then you would have to link all of the symbol files to the appropriate extension modules and dll files. then and only then would I get a debugging output that I would know what is actually taking place.

that's a lot of work. and I do not have a problem doing it. But before we do it I need to have some questions answered.

What version of EG?
What version of Windows?
Is it an upgrade of EG or a clean install?
If it is an upgrade have you tried a clean install?
Have you tried renaming your config.py file ? (this will cause EG to build a new one)
Have you tried renaming the saved config tree file? (this will cause EG to load the default one)
Have you tried the last 2 questions together?
Have you removed all plugins except for the core installed ones? (plugin locations are c:\program files (x86)\eventghost\plugins and c:\programdata\eventghost\plugins)

scratch the Windows version question. I can see you are running Windows 7 build 7601 (sp1)

wow thanks for the timely reply K

What version of EG?

EventGhost_WIP-2019.03.10-20.11.47_Setup

Is it an upgrade of EG or a clean install?

upgrade

If it is an upgrade have you tried a clean install?

i know i should have tried a clean install but i .... am lazy.
i guess my first step will be clean install, then add each plugin one by one, then if it still hasn't crashed at that point i will try loading my .xml tree

-Have you tried renaming your config.py file ? (this will cause EG to build a new one)
-Have you tried renaming the saved config tree file? (this will cause EG to load the default one)
-Have you tried the last 2 questions together?
-Have you removed all plugins except for the core installed ones? (plugin locations are c:\program files (x86)\eventghost\plugins and c:\programdata\eventghost\plugins)

aren't these irrelevant if i try a clean install?

if you uninstall eventghost it does not delete any user files. so files in %appdata%\eventghost and in %programdata%\eventghost which is the location where the config.py file is located and also any plugins you have installed, these paths do not get removed. and upon installing eventghost again the files will get used again.

I am willing to be that it is a plugin causing the problem. I need to know what plugin in order to repair it.

I also wanted to note that if a plugin is not installed in your tree but it is in either of the plugin paths i listed in an earlier post and you have debugging enable the plugin does get loaded and can cause a crash. so be sure to move any plugins that are not "Factory" shipped with EG to another folder. then one at a time move them back. restart EG if you do not get a crash then add the plugin to the tree. if no crash then remove the plugin from the tree. save and close EG move the next one over and start EG again. keep doing this until all plugins have been added.


so this is how you will want to start the process..


Uninstall EG.
Create a folder on your desktop called backup.
in the backup folder create 3 folders. one called programfiles another called program data and the last called appdata

go to c:\program files (x86)
locate the EventGhost folder (if any)
move the eventghost folder to backup\programfiles on your desktop.
you want to key this into the path bar at the top of the file explorer
%appdata%
locate the eventghost folder.
move the eventghost folder to backup\appdata
key this into the path bar
%programdata%
find the eventghost folder.
move the folder to backup\programdata

then install EG

Software
Program Version: WIP-2019.03.10-20.11.47, Build Time: Sun, 10 Mar 2019 20:11:47
Python Version: Stackless Python 2.7.15 final 0, wxPython Version: 3.0.2.0

System
Operating System: Microsoft Windows 7 Enterprise SP1, 64-bit (build 7601)
CPU: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
RAM: 15.9 GB
--

Hmm, this seems to have been quite easy to fix. Let us hope i won't run into any more issues down the road with the new WIP EG.
troubleshooting detailed below.


troubleshooting process part 1:
1. clean install of EventGhost_WIP-2019.03.10-20.11.47_Setup.exe
2. reboot
3. tried starting WIP-2019.03.10-20.11.47 = no crash on startup

i have now isolated the non-factory plugins that i'm using:
- AudioEndpoint
- AutoRemote
- LogRedirector
- PhilipsHue
- PotPlayer
- ZWave-0.5.3b.egplugin

troubleshooting process part 2:
1. add potplayer plugin to factory tree = no crash on startup
2. add Plugin: USB-UIRT to factory tree = no crash on startup
3. added Plugin: AudioEndpoint to factory tree = no crash on startup
4. added Plugin: Philips Hue to factory tree = no crash on startup
4. added Plugin: AutoRemote to factory tree = no crash on startup
5. added Plugin: LogRedirector to factory tree = no crash on startup

6. added ZWave-0.5.3b.egplugin to factory tree..........

when trying to save tree after adding Zwave, result is:
.... but then i exited EG without saving the tree and re-added ZWave-0.5.3b to tree, which resulted in:
"Z-Wave: Finished initializing new network."
..... and saving the tree afterwards gave no errors!

7. did a couple more restarts of EG to make sure it still works = no crash on startup

8. i will now do a "troubleshooter's leap of faith" and load my regular .xml tree into EG WIP-2019.03.10-20.11.47 = no errors!!

9. restarting EG with my regular tree loaded = only error now is "Z-Wave: Room not found."

10. re-adding my backed-up Zwave settings into %programdata% and launching EG = no errors, but EG takes 20 seconds to initialize (my Zwave rooms have been re-added successfully)
11. rebooting Windows just to make sure = EG launches with no errors


my conclusion:
something in %AppData% was haunting the new EventGhost (no pun intended, i swear)

Ahhh yes... you are supposed to get the appcrash when you upgraded EG.

there is a bug in python 2.7.12 in the core of it that causes an appcrash when running a compiled cython extension. I had spent a year working with the developers of cython and with stackless python to fix this bug. and we did. but in order to get the zwave plugin to the users I had to make the plugin so it would replace the core python files in eventghost. so when you upgraded the version of EG it put the old files back into place. I had not thought of this being a potential problem. At this point I am not going to be concerned with fixing it because a new version of python has been released with these bug fixes added to the core. I will be updating the version of python in the next release candidate and I will no longer need to swap any files around. I am truly sorry you had to go through this process. I should have remembered that the zwave plugin caused the appcrash problem. I will lets users also know in the zwave help topic about this.

so long as you reinstalled the plugin you should be good to go. the only thing that needs to be done is after the upgrade there are 3 files with .backup on the end of them thsat are located in the root of the eventghost directory that have to be deleted. There is another correction I have to make to the plugin that I discovered as well. the filenames it is trying to replace are incorrect.

kgschlosser wrote: Sun Mar 24, 2019 4:38 pm Ahhh yes... you are supposed to get the appcrash when you upgraded EG.

there is a bug in python 2.7.12 in the core of it that causes an appcrash when running a compiled cython extension. I had spent a year working with the developers of cython and with stackless python to fix this bug. and we did. but in order to get the zwave plugin to the users I had to make the plugin so it would replace the core python files in eventghost. so when you upgraded the version of EG it put the old files back into place. I had not thought of this being a potential problem. At this point I am not going to be concerned with fixing it because a new version of python has been released with these bug fixes added to the core. I will be updating the version of python in the next release candidate and I will no longer need to swap any files around. I am truly sorry you had to go through this process. I should have remembered that the zwave plugin caused the appcrash problem. I will lets users also know in the zwave help topic about this.

so long as you reinstalled the plugin you should be good to go. the only thing that needs to be done is after the upgrade there are 3 files with .backup on the end of them thsat are located in the root of the eventghost directory that have to be deleted. There is another correction I have to make to the plugin that I discovered as well. the filenames it is trying to replace are incorrect.

well i managed to seemingly fix the issue and i jogged your memory, so it's all good.

there are much much worse things in life

There are. but i did make you spend some time working on this issue when I should have remember that this kind of a thing could have happened.

Thankfully this will be something that is going to go away in time

kgschlosser wrote: Sun Mar 24, 2019 6:06 pm There are. but i did make you spend some time working on this issue when I should have remember that this kind of a thing could have happened.

Thankfully this will be something that is going to go away in time