When receiving encrypted remote updates, and when the encryption key isn't available "e.g. Enter Passphrase screen", the Worker keeps tracks of the incoming updates in a map keyed on server_id.

When the encryption key is available, the worker iterates over the map, decrypts the entities and passes them over to the Processor.

As a results, the order updates isn't preserved across that process.

For Hierarchical data types such as Bookmarks, the entities are expected to arrive in the same order as sent from the server.

One solution is to store the entities in a vector instead of map, but that would be a memory regression because it can grow faster than the map in case of updates having the same server id.

However, fixing crbug.com/831160 would solve the issue.