Closes 20975: Run metadata cleanup after Megazord.init()
This ensures that we do not attempt places initialization before Megazord.init() finishes, and that touching BrowserStore does not kick-off places initialization (due to the `cleanup` call being a side-effect of creating metadata middleware, used as part of the BrowserStore). Glean initialization happens before initialize megazord, and it touches core.store BrowserStore instance, kicking-off places initialization on an IO thread (due to the cleanup call), which raced megazord initialization on the main thread. App init sequence is a bit of a mine-field, so this patch takes the easy way out and doesn't attempt to re-order initialization sequence. Also, initializing places as a side-effect of touching BrowserStore was also, clearly, a bug.upstream-sync
parent
950b2332d6
commit
6161dc6e8d
Loading…
Reference in New Issue