dmarmor
dmarmor
@icotext, were you launching an app under normal circumstances when that error happened, or was it on reboot or some otherr special context?
So the problem here has to do with the app engine, which lives in the Engine.noindex folder in the app's config directory (under Library/Application Support/Epichrome/Apps). For some reason, it's not...
So yeah, if for whatever reason the helper app doesn't launch properly, or dies unexpectedly, then the app engine doesn't get deactivated, and in that case launching it directly will...
Hi @GrogHills, are you sure you didn't run the app again before capturing this log file? The log shows the app finding a running engine and the cleanup helper launching...
Hi @GrogHills, I've tried to address the flakiness of Apple's app-launching in beta 9 (up on Patreon in the next day or so), so hopefully this type of error shouldn't...
This has been resolved as best I can in 2.3.0 within the limits of the architecture of Epichrome. It's still possible for the engine to get left in an activated...
Hey @talleux, moving this here to merge with the previous discussions on this issue. > hmmm. i just had the same now (my bloody new MBP 16 like to crash...
Hi @talleux , sorry this happened. Currently the best solution is the one you did and which appears to have worked. Did you get that Unable to Run dialog box...
Yes! I would love to see that log. If you can send me the whole Logs folder that would be ideal. If you don't want to post it here, just...
Hey @talleux was this meant to go into issue #232? It looks like the same issue.