UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
Steps to reproduce the problem:
1. Add macro TRACE_EVENT0 to the function TemplateURLPrepopulateData::GetEngineType().
2. Change the default search engine to Yandex or Nigma.
3. Activate tracing and type some words to the omnibox
4. See that TemplateURLPrepopulateData::GetEngineType() uses too much CPU time (about 28% of the wall duration of AutocompleteController::Start()).
What is the expected behavior?
TemplateURLPrepopulateData::GetEngineType() uses nearly zero CPU time.
What went wrong?
TemplateURLPrepopulateData::GetEngineType() uses too much CPU time.
Did this work before? N/A
Chrome version: <Copy from: 'about:version'> Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0
If the default search is Google then TemplateURLPrepopulateData::GetEngineType() uses much lesser CPU time. See my screenshotes for details.
|
Deleted:
GetEngineType_DefaultIsYandex.png
51.9 KB
|
|
Deleted:
GetEngineType_DefaultIsNigma.png
51.9 KB
|
|
Deleted:
GetEngineType_DefaultIsGoogle.png
52.2 KB
|
Comment 1 by vit...@yandex-team.ru
, May 17 2016