Hello,
I am having an issues where tasks scheduled via posttask, if they throw, will crash the my process. Its extremely hard to debug these issues and im looking to tighten up my implementation and understand more of the mechanics at play here.
Ive tried try-catch statements around method blocks inside of the tasks, and they dont work... Is this a situation where CEF has just crashed my process for some reason and not the code that is throwing and thats why my try-catches dont work?
On a related note, is there guidance on getting the cef debug symbols going with cefglue? When these crashes happen, i sometimes i dont get much context at all. Sometimes CEF is really helpful, and gives me nice asserts or similiar that i can research. But other times, the stack is light on, and doesnt give much humean readable information. In these cases, I cant tell if its my code which is throwing or if its CEF killing me or what...? ive tried to use the debug_symbols by renamed to `libcef.dSYM` and placing in `frameworks` or `monobundle` and it doesnt give me any extra info in the stack at all...
Im currently debugging multiple issues with my App and have a sample implementation here.
https://github.com/captainjono/Chromely/issues/1
Right now ive just tried to integrate these fixes into my existing app, and when i call quitmessageloop() , its calling out to cef which is crashing the process I have no idea why. Verbose logging shows nothing. So im guessing...! would like a more structured approach!