Comment #20 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=32319
------------------------------------------------------------------------
r32319 | [email protected] | 2009-11-18 03:07:40 -0800 (Wed, 18 Nov 2009)
| 10 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/in_process_webkit/dom_storage_dispatcher_host.cc?r1=32319&r2=32318
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/in_process_webkit/dom_storage_dispatcher_host.h?r1=32319&r2=32318
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/in_process_webkit/webkit_thread.cc?r1=32319&r2=32318
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/in_process_webkit/webkit_thread.h?r1=32319&r2=32318
Make the WebKitThread object start the WebKit thread on construction (not
lazily).
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.
TEST=The WebKit thread gets spun up early in the initialization process.
BUG=24144
Review URL: http://codereview.chromium.org/405007
------------------------------------------------------------------------
--
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
