Hi,
From the log we see that GetThreadContext was not supported and is failing --- however this is not the primary point of failure. GetThreadContext is called to capture call stack when the browser engine crashes. So another crash occurred first. However since we are not able to capture the crashing call stack due to GetThreadContext not being supported, we are unable to trace back to the original point of failure.
Nevertheless, even if we could trace it back to the original point of failure, most likely we will not be able to resolve it. This is because most of the time we are not in a position to modify the browser engine. So if a specific feature of the browser engine depends on something ThinApp does not support, then most likely there is nothing we can do on our end. If Chromium has a built-in flag/switch that can bypass the problematic code path, then it could work. Otherwise we won't be able to modify it just to make it work with ThinApp. Additionally, since ThinApp encaptures everythings in a single application, it is not possible for us to attach a debugger to debug a specific process running inside it the traditionally way.
One thing you can try is to run x86 build instead. The most siginficaint change in 2022 release cycle is the default build runs browser engine in x64 mode, where as earlier versions run browser engine in x86 mode. However we still offer x86 build upon request. So you can try that build and see if it works for you. We will PM you with the x86 build download location.
We do not maintain a table showing Chromium version of each release. However you can load "chrome://version" to view Chromium version. You can also use this method to get the browser engine at runtime:
https://www.essentialobjects.com/doc/jsdoc.public.webengine.eoapi.htmlHope this helps.
Thanks!