v113.0.5672.62-2

Backported upstream security fix that fixes a crash.

https://chromium-review.googlesource.com/c/chromium/src/+/4437791
https://crbug.com/1428820

(Withdrawn) v113.0.5672.62-1

Rebased to 113.0.5672.62.

Reported to have crash #502

v112.0.5615.49-1

Rebased to 112.0.5615.49.

v111.0.5563.64-1

Rebased to 111.0.5563.64.

v110.0.5481.100-1

Rebased to 110.0.5481.100.

v109.0.5414.74-2

Fixed AIA chasing on Mac

v109.0.5414.74-1

Rebased to 109.0.5414.74.

v108.0.5359.94-1

Rebased to 108.0.5359.94.

v107.0.5304.87-3

Fix a trap on Asus Merlin devices.

v107.0.5304.87-2

Fix a crash on Mac.

The crash is caused by the static initializer for setting up PartitionAlloc on Mac being accidentally optimized out by the linker, resulting in undefined behavior in accessing uninitialized thread local storage during PartitionAlloc thread cache purge.

This could happen because our code relies on the default behavior of PartitionAlloc instead of the mainstream procedure used by the browser processes. The fix adopts much of the PartitionAlloc initialization procedure used by the full browser with the following simplifications:

• No PCScan
• No Backup Ref Ptr checks
• No RawPtr checks

New behaviors also enabled by this fix:

• Enabled PartitionAlloc Thread Cache previously disabled. This offers a very small performance gain because allocations are few, but this code path is more mainstream thus more likely to be well tested.
• Enabled PartitionAlloc in all OpenWrt builds. OpenWrt builds previously disabled PartitionAlloc entirely because of issues with Musl, which have been fixed this time. This should have non-trivial improvement in allocation by replacing libc malloc. See https://blog.chromium.org/2021/04/efficient-and-safe-allocations-everywhere.html about the nature of this improvement.