-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on startup after update #1721
Comments
Are you able to eventually close out of the error dialog and get to the about dialog (Help > About)? If so, can you post a screenshot here. It's super weird that this is happening, since this is part of the |
The error triggers before the main screen comes up. EDIT: If I close out of the error, the main screen does not appear either, and I need to force close Pyfa to free up system resources. |
@BlueThrowaway37 Hrm... can you check if you have a pyfa directory at this location:
If so, does it have an eve.db file in it? If so, can you zip that up and upload to this thread? Additionally, navigate to where pyfa was installed with the exe and find the eve.db file and zip/upload that one as well please I just tested the virtual store issue, and recent installers still remove the VirtualStore directory. The only other way I could think this may happen is if you installed using exe, and then unzipped another version on top of that (in which case, the installer isn't run which is what cleans up the virtual store directories). But even then, I thought we fixed that within the packaging process itself. :/ Anyway, would be helpful to get those additional files. |
eve-AppData is the eve.db file from the AppData VirtualStore directory |
Are you sure you used the installer? Could you uninstall and then reinstall using the .exe file and see if that helps? Indeed, the VirtualStore is keeping a copy of an old Did you come back after a bit of a break by chance? One where you didn't update pyfa regularly? |
I just tried uninstall/reinstall, both with 2.5.0 beta and then first with the 2.3.0 stable then 2.5.0 beta. Problem is still occurring. I did come back form a break, but not recently. I've been successfully using pyfa since the 2.0.0 update and keeping it fairly regularly updated to stable. |
k, as a last resort, if you could do the following, that would be amazing
You could probably get away with deleting the VirtualStore and just using the latest release, but I don't want us to get another release or two in the future and find out that there's still an issue. If we can install each version and see if we can reproduce and figure out exactly which version bump seems to be causing this, that would be ideal. The eve data versions should roughly match the following (earlier versions may or may not reflect this exactly, since they were hit with the VirtualStore issue):
I know that's tedious, but I think that would give me as much information as I could collect. If nothing comes of it, then we can chaulk it up to it simply being a fluke. Let me know what you find :) |
Finally able to spend time doing the uninstall/reinstall cycle... Results: Error log:
|
Will try removing the appdata store again and see if 2.3.0 to 2.4.0 or 2.5.0b1 has issues. Clearing the AppData store and installing directly to the most recent beta release appears to work! |
I also went through the reinstall cycle
This did not happen for me... So weird. Did you try going from 2.3.0 > 2.4.0 > 2.5.0b1? Or did you just go straight to latest release? I'm still concerned that your system, for whatever reason, doesn't delete the virtual store correctly. |
Oh damn... think I figured it out kk, 2.1.1 is the version in which the installer should remove the virtual store. However, that was supposed to be more of a cleanup, not an actual fix. The actual fix was to tweak the exe in a way that Windows wouldn't use the virtual store. I think for that release it was a manual process, with the intension of making it automated. Don't think I ever got it to be automated... I'll take another dive into that issue. Still not sure why your installer isn't removing old files from the VirtualStore, but that's besides the point. I'll keep this issue updated as to progress :) |
Unable to open updated install after 2.3.0 release. Program crashes at startup and gives the following logfile as an error. Program was installed from .exe rather than source. Problem was encountered starting with 2.3.1 stable release .exe
Release: 2.3.1 stable to 2.5.0b1
The text was updated successfully, but these errors were encountered: