summaryrefslogtreecommitdiffstats
path: root/chrome/browser/history/text_database_manager.cc
diff options
context:
space:
mode:
authorestade@chromium.org <estade@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-10-02 04:53:59 +0000
committerestade@chromium.org <estade@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-10-02 04:53:59 +0000
commiteb6f2c542d7405788d668a762282b66655836e1d (patch)
tree3e7558d38c45c9e9620455669444b2755d608413 /chrome/browser/history/text_database_manager.cc
parent63af5a4251dfae13ae831d87c68b201e70a49530 (diff)
downloadchromium_src-eb6f2c542d7405788d668a762282b66655836e1d.zip
chromium_src-eb6f2c542d7405788d668a762282b66655836e1d.tar.gz
chromium_src-eb6f2c542d7405788d668a762282b66655836e1d.tar.bz2
Make sudden termination into a counter.
We were incorrectly interpreting enableSuddenTermination to mean "enable sudden termination". Really it should just decrement a counter, and we should only enable sudden termination when that counter reaches 0. Related to, but not the fix for, http://crbug.com/5638 This may have been causing memory corruption due to shutting down the renderer process while writing to a storage area or icon database (although honestly I don't actually know if we even use those parts of webkit). Also, add a ui test that fails before this patch and succeeds with this patch. BUG=none TEST=sudden termination still works on a simple page Review URL: http://codereview.chromium.org/245036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27831 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/history/text_database_manager.cc')
0 files changed, 0 insertions, 0 deletions