Move ModuleUtil init to after the chrome ClassLoader is available
ModuleUtil.initApplication() ends up calling SplitCompat.install() with the application context. We need to make sure the application context ClassLoader has been replaced by the chrome ClassLoader at this point, otherwise SplitCompat may not be able to load fake installed splits. This is a bit unfortunate since ModuleUtil.initApplication() is pretty expensive, and the chrome module will no longer be able to preload in parallel, but not sure if there's much that can be done about that. Bug: 1158024 Change-Id: Ie81f7b85100707ed1e8273f57553812918c08a23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593518Reviewed-by:Andrew Grieve <agrieve@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#837607}
Showing
Please register or sign in to comment