summaryrefslogtreecommitdiff
path: root/media/libeffects/visualizer/EffectVisualizer.cpp
diff options
context:
space:
mode:
authorJeff Brown <jeffbrown@google.com>2012-03-22 18:05:39 -0700
committerJeff Brown <jeffbrown@google.com>2012-03-22 18:11:55 -0700
commit9ac2d3bcde40abce8ab8af56560ea6b3ee5f9941 (patch)
tree961195d616d6efca45b28254ce671dd70e0f1c49 /media/libeffects/visualizer/EffectVisualizer.cpp
parentd67c8c67899481682657d41a61f3846b8d77d165 (diff)
Do not enable WAL mode for the WebView database.
There is no need to enable WAL for the WebView database because it does not require high throughput. Enabling WAL increases memory usage and can also cause problems if the same database is opened in multiple processes, which can happen if an application has UI code running in multiple processes. Normally, we would use a content provider to ensure that the database is only opened within one process (and then accessed remotely view RPC), but we can't do that for WebView because it is part of the framework. Deleted the call to setLockingEnabled. It does nothing. Bug: 6124556 Change-Id: Ic397c74872fe6b1246da0c859eab0d5147045c86
Diffstat (limited to 'media/libeffects/visualizer/EffectVisualizer.cpp')
0 files changed, 0 insertions, 0 deletions