Francois Marier ef8ea55aca Bug 1434206 - Keep TableUpdate objects in smart pointers. r=gcp ...

Manually keeping tabs on the lifetime of these objects is a pain
and is the likely source of some of our crashes. I suspect we might
also be leaking memory.

This change creates an explicit copy of the main array into the
update thread to avoid using a non-thread-safe shared data
structure. This is a shallow copy. Only the pointers to the
TableUpdates are copied, which means one pointer per list (e.g. 5
in total for google4 in a new profile).

MozReview-Commit-ID: 221d6GkKt0M

2018-06-01 15:48:48 -07:00

33 KiB

Raw Blame History

View Raw