Unexpected error with CR 1.2.2: do I have to roll back to 1.2.1 ?

Since I updated to 1.2.2 I have had a lot of “Unexpected errors” or “internal errors”. I updated my nvidia driver to the last studio version, I am using the CR default values but still I get these errors. What is surprising is that I get these errors even with old datasets which were proceeded without any problem with v1.2.1.
Even the uploading the log after a fatal error does not work.
Are you preparing a fix for this 1.2.2 version which looks to me a not stable beta version or do I have to roll back to v1.2.1 ?

No answer? I just tested again v1.2.2 and again a lot of “unexpected error” (here for a normal reconstruction). The same dataset is working fine with v1.2.1.
Are you going to fix this broken upgrade?