Open Wyrrrd opened 2 years ago
(I get that the bot's crashing possibility is in the description of the feature, therefore expected. I opened this issue to give a detailed description of the behaviour, in case you plan to fix it. Feel free to close if the feature should stay experimental.)
CC @drblaui
@Wyrrrd If you could run it from the command line that would maybe yield some more details. Ideally even run it from source in development mode and then open the DevTools...
CLI output seems not too helpful, as far as I can see it just reports missing objects after they went missing.
This is crazy, I have no idea why this even breaks that badly.
But maybe it can be fixed very hacky: What if we catch the "errors" and just skip them? If the item doesn't exist, why bother doing something with it. Is there an easy way to just skip these elements maybe?
@drblaui I think this is already the behavior for all non-essential elements, but please double-check. My guess: there is an error that is not showing in the logs happening first and everything thereafter is an irrelevant side-effect of the UI going wry producing many verbose (already caught) errors. I've opened #116 to track an improvement on the logging.
You probably know your code best. Do you think there is an error you're not logging? As far as I can see the amount of logging is generally thorough. Also non logged errors should kill the whole electron process and not just logic/UI?
After some reloads, the bot overlay (bot image, speech bubbles, flat parameter evaluation) disappears and the bot is stuck on reloading the page repeatedly (more often than normally expected).