Comment #31 on issue 24144 by [email protected]: chrome crash in debug
build when openning a link with UTF8 character in it
http://code.google.com/p/chromium/issues/detail?id=24144
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=33170
------------------------------------------------------------------------
r33170 | [email protected] | 2009-11-25 19:03:18 -0800 (Wed, 25 Nov 2009)
| 25 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/browser/in_process_webkit/dom_storage_dispatcher_host.cc?r1=33170&r2=33169
M
http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/browser/in_process_webkit/dom_storage_dispatcher_host.h?r1=33170&r2=33169
M
http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/browser/in_process_webkit/webkit_thread.cc?r1=33170&r2=33169
M
http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/browser/in_process_webkit/webkit_thread.h?r1=33170&r2=33169
M
http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/browser/renderer_host/resource_dispatcher_host.cc?r1=33170&r2=33169
Merge 33144 - RESUBMIT of http://codereview.chromium.org/404025/show
Start the WebKit thread when we initialize the resource
dispatcher host.
NOTE: It's very possible this will have a startup
performance impact. I'm going to watch the bots after
committing.
TODO: Clean up shutdown logic that exists simply
because we don't know whether or not we'll ever start
the WebKit thread.
Originally landed in r33063, reverted in r33101 due to
coincidence with Modules Linux startup test failures.
TBR=jorlow, darin
TEST=The WebKit thread gets spun up early in the
initialization process.
BUG=24144,28364
Review URL: http://codereview.chromium.org/441025
[email protected]
Review URL: http://codereview.chromium.org/443014
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
