Fix cause of uninitialized memory read in ExtensionService unit_tests
In crrev.com/113111 I checked in code that reads a app state boolean from an ExtensionSyncData object which is uninitialized. This fixes the initialization for the relevant constructor, and also limits reading that value to only when the extension is an app. BUG=106549 TEST=valgrind run of ExtensionService sync-related unit_tests should come back clean Review URL: http://codereview.chromium.org/8899010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113926 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment