Issue 3051: REGRESSION: 6% perf regression in startup tests after the merge http://code.google.com/p/chromium/issues/detail?id=3051
Comment #4 by [EMAIL PROTECTED]: Tony, how were you measuring / profiling? initializeThreading() triggers an exception to set the thread name in a debugger. This makes it hard to follow the control flow, because you have to follow the exception being handled. I was just testing a trace in windbg, and it thinks this function never returns, and thinks that all code executed after initializeThreading() is still within it. That said, I'm still unsure why we need to initialize this code. It creates a Window used for dispatching some messages... would be nice to avoid it if we can. I'm not sure this is where the regression lies through, try commenting out the setThreadName call. -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
