We had exactly this problem in one (and only 1) of our cloud environments. As in the cloud we do not have direct access to the servers, it had to be corrected via support ticket.
The fix was just renaming the folder and let the component create a new one.
Is there a chance of adding some kind of protection to the component in these cases? For example, some kind of reset in which you delete the C:\Windows\Temp\.local-chromium\ folders and create new ones? It would be very useful for those in the cloud.
Thank you.