Comment #13 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 WebKit thread is currently initialized lazily. If we want this code to work as is, then we'll need to always initialize it and do so fairly early in the startup of the browser it seems. Can we convert UTF-8 strings to UTF-16 (or something that doesn't require that data structure being initialized)? If so, I think we might be able to solve this. On the other hand, it might just be a matter of time until we have to spin up the WebKit thread early on for some other similar reason. -- 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
