Bug 484882: Synchronize access to fSortedConfigNames

The new test demonstrates the problem by running two threads,
one creating/deleting launch configs, the other one accessing
fSortedConfigNames.

Note if you set fSortedConfigNames to volatile without making 
clearConfigNameCache synchronized you can see the test fails
generally very fast.

Change-Id: I981d7054d51e263f5d097096ffe23cdc1fa74256
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
2 files changed