diff options
| author | senorblanco@chromium.org <senorblanco@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-04-29 21:31:13 +0000 |
|---|---|---|
| committer | senorblanco@chromium.org <senorblanco@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-04-29 21:31:13 +0000 |
| commit | ec8a3ea52935ef57bfcf5597300f9284e2cfa9f2 (patch) | |
| tree | a486fe4c712e7a0592f497edd933a4245cfb6f97 /chrome/app/DEPS | |
| parent | 313b4919bf602a4b20bf7e8e0586d613b3fa5dc2 (diff) | |
| download | chromium_src-ec8a3ea52935ef57bfcf5597300f9284e2cfa9f2.zip chromium_src-ec8a3ea52935ef57bfcf5597300f9284e2cfa9f2.tar.gz chromium_src-ec8a3ea52935ef57bfcf5597300f9284e2cfa9f2.tar.bz2 | |
A better fix for http://www.crbug.com/2044: crash
on large <canvas> elements. We disable the __debugbreak
only when skia tells us it is prepared to correctly
handle a failed (NULL) malloc(). It does this
by calling sk_malloc_flags() without SK_MALLOC_THROW.
Note that, since the switch to tcmalloc, the new_handler
was not getting called at all (since tcmalloc doesn't
support it yet), so this crash is currently unreproducible
in trunk. In order to test this change, I reverted the
tcmalloc change in my client. This is not the case in the
stable branch, since it doesn't use tcmalloc, so this change
is still needed there. (It will also be needed in trunk
again once mbelshe's re-implementation of the new_handler
is in).
BUG=http://www.crbug.com/2044
Review URL: http://codereview.chromium.org/100163
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14891 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/app/DEPS')
| -rw-r--r-- | chrome/app/DEPS | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/chrome/app/DEPS b/chrome/app/DEPS index 8f26006..4b3b7c1 100644 --- a/chrome/app/DEPS +++ b/chrome/app/DEPS @@ -4,5 +4,6 @@ include_rules = [ "+chrome/installer", "+chrome/personalization", "+sandbox", + "+skia/include/corecg", "+tools/memory_watcher", ] |