dmarmor
dmarmor
It should be at: ``` ~/Library/Application Support/Epichrome/Apps//Logs ```
Oh, sorry for the confusion, the log won't be in Console. If you go to that directory in Finder or Terminal, you should find a bunch of text files there...
Hi @bryanyork, did killing process 15850 help? Or did it just repeat the same problem on the next run? I suspect this might be related to Issue #248. Can you...
Well, I'm glad it's at least improved for now. If you can update that app to 2.3.3 or 2.3.4, hopefully it won't recur...
Hi @matthewfallshaw, yeah, it looks like some zombie version of the app was left running. I'm not sure how that happened, but the good news is that it shouldn't be...
Hi @rjackson-dev-ops, it looks to me like the problem you were experiencing here is that for some reason you couldn't see the GitHub update dialog. I'm not sure why that'd...
This is probably a result of the app/engine architecture of Epichrome. Version 2.4 is going to change that architecture and hopefully you won't see this problem any more at that...
Sounds good, thanks!
At first glance, these are completely mystifying to me. I will take a look, hopefully over the weekend, and let you know what I find. Thanks for the report.
OK, I think I see what's happening here. This app is on 2.3.0b2, which is a very early beta and cannot be directly updated to 2.3.2. Unfortunately, what you'll have...