This is a known issue documented here.
The issue has been identified as a Chrome issue than the salesforce issue. The timing of the chrome issue and Salesforce release is a coincidence. You can follow the bug here
Hopefully, this will be resolved with the next Chrome update.