These hangs during deserialization seem to have started appearing around 66:

https://crash.corp.google.com/browse?q=product.version+LIKE+%276%25%27+AND+expanded_custom_data.ChromeCrashProto.ptype%3D%27renderer%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name+like+%27%5BRenderer+hang%5D+v8%3A%3Ainternal%3A%3ADeserializer%25%27+AND+expanded_custom_data.ChromeCrashProto.channel%3D%27%27#-propertyselector,productname:1000,productversion:100,magicsignature:50,-magicsignature2:50,-stablesignature:50,magicsignaturesorted:50

The backtraces point into the deserializer, but aren't consistent beyond that. It's in both context- and isolate-deserialization, and the exact hang sites differ.

It seems strange that only some clients hang, since all use the same snapshot file. That may point at external causes like disk corruption or a slow system.

Let's keep an eye on this.