Make the browser survive massive data: URIs, via various techniques:...

chrome/common/chrome_constants.h

 // Copyright (c) 2006-2008 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // A handful of resource-like constants related to the Chrome application.
 
 #ifndef CHROME_COMMON_CHROME_CONSTANTS_H_
 #define CHROME_COMMON_CHROME_CONSTANTS_H_
 
 #include "base/file_path.h"
@@ skipping 56 matching lines @@
 extern const unsigned int kMaxRendererProcessCount;
 extern const int kStatsMaxThreads;
 extern const int kStatsMaxCounters;
 
 // The maximum number of characters of the document's title that we're willing
 // to accept in the browser process.
 extern const size_t kMaxTitleChars;
 // The maximum number of characters in the URL that we're willing to accept
 // in the browser process. It is set low enough to avoid damage to the browser
 // but high enough that a web site can abuse location.hash for a little storage.
+// We have different values for "max accepted" and "max displayed" because
+// a data: URI may be legitimately massive, but the full URI would kill all
+// known operating systems if you dropped it into a UI control.
 extern const size_t kMaxURLChars;
+extern const size_t kMaxURLDisplayChars;
 
 extern const bool kRecordModeEnabled;
 
 extern const int kHistogramSynchronizerReservedSequenceNumber;
 
 // The maximum number of session history entries per tab.
 extern const int kMaxSessionHistoryEntries;
 
 extern const wchar_t kChromiumRendererIdProperty[];
 
 }  // namespace chrome
 
 #endif  // CHROME_COMMON_CHROME_CONSTANTS_H_