New issue
Advanced search Search tips

Issue 628552 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome is glacially slow to open itself and when visiting the first webpage in a new tab

Reported by o...@outlook.com, Jul 15 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome
2. Wait ~15 seconds
   (Chrome opens)
3. Add a new tab
   (Tab opens almost instantly as usual)
4. Type "google.co.uk" in the address bar
5. Press Enter
6. Wait ~5 seconds
   (Webpage starts to load)

What is the expected behavior?
Steps 2 and 6 (where one must wait) should not be required

What went wrong?
Steps 2 and 6 are required

Did this work before? Yes In version 50

Chrome version: 51.0.2704.106  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0

This issue did begin occurring immediately after updating to version 51.0.2704.106. 

When waiting for the first website to load after opening a new tab the process responsible for that tab uses 100% of a CPU core, after loading the first webpage further navigation is no slower than before.

When the browser takes ~15 seconds to load 100% of the CPU is in use (all cores not just 1) and the process responsible for this comes up as "Utility: JSON Parser" in the Google Chrome task manager. (I only managed to catch this process description using an AHK script to open Chrome and then the internal task manager and take a screenshot. As no human would be fast enough to catch this manually.)

I am running EMET. However disabling this DOES NOT FIX THE ISSUE.

I use Bitdefender as my antimalware product. However disableing this DOES NOT FIX THE ISSUe.

I have tried enabling and disabling hardware acceleration this MAKES NO DIFFERENCE.

Here are two stack traces of the main thread of the tab process that is using 100% of one core while loading the forst webpage. They were taken sequentially a few seconds apart, on the same tab during the loading of the same webpage during the same peak in CPU core activity.

0, ntoskrnl.exe!_misaligned_access+0x1833
1, ntoskrnl.exe!IoFreeErrorLogEntry+0x297
2, avc3.sys!SetAvckfStopRoutine+0x2af44
3, avc3.sys!StartProfilingTimer+0x20178
4, avc3.sys!SetAvckfStopRoutine+0x2d82d
5, avc3.sys!SetAvckfStopRoutine+0x220bc
6, avc3.sys!SetAvckfStopRoutine+0x1997f
7, avc3.sys!DllUnload+0xc557
8, avc3.sys!StartProfilingTimer+0x1f4a0
9, ntoskrnl.exe!NtCreateFile+0x34e
10, ntoskrnl.exe!NtMapViewOfSection+0x1c0a
11, ntoskrnl.exe!NtDeviceIoControlFile+0x56
12, ntoskrnl.exe!KeSynchronizeExecution+0x3a23
13, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
14, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x1fb
15, wow64.dll!Wow64SystemServiceEx+0x1ce
16, wow64.dll!Wow64LdrpInitialize+0x42a
17, ntdll.dll!RtlUniform+0x6e6
18, ntdll.dll!EtwEventSetInformation+0x1da09
19, ntdll.dll!LdrInitializeThunk+0xe
20, ntdll.dll!NtDeviceIoControlFile+0x15
21, kernel32.dll!DeviceIoControl+0x48
22, avcuf32.dll!AvcGetJumpCode+0x1eb4d
23, avcuf32.dll!AvcGetJumpCode+0x3c94
24, avcuf32.dll!AvcGetJumpCode+0x1396f
25, avcuf32.dll!AvcGetJumpCode+0x3fb80
26, avcuf32.dll!AvcGetJumpCode+0x7c647
27, avcuf32.dll!AvcGetJumpCode+0xa43d
28, EMET.dll!GetHookAPIs+0x37e29
29, EMET.dll!GetHookAPIs+0x37d7b
30, ntdll.dll!RtlGetProcessHeaps+0x49d
31, ntdll.dll!RtlCaptureContext+0x187
32, ntdll.dll!RtlDestroyEnvironment+0x384
33, ntdll.dll!KiUserExceptionDispatcher+0xf
34, ntdll.dll!RtlEncodeSystemPointer+0x51f
35, ntdll.dll!RtlSetBits+0x11b
36, ntdll.dll!RtlSetBits+0x16b
37, ntdll.dll!RtlSetBits+0x60
38, ntdll.dll!RtlGetFullPathName_U+0x36d
39, ntdll.dll!RtlUlonglongByteSwap+0x68f
40, EMET.dll+0x27189
41, EMET.dll!EMETSendCert+0xff7
42, EMET.dll!EMETSendCert+0xebc
43, EMET.dll+0x27161
44, KernelBase.dll!SetThreadStackGuarantee+0xa37
45, KernelBase.dll!LoadLibraryExW+0x233
46, ntdll.dll!RtlQueryPerformanceCounter+0xa83

0, ntoskrnl.exe!_misaligned_access+0x1833
1, ntoskrnl.exe!IoFreeErrorLogEntry+0x297
2, avc3.sys!StartProfilingTimer+0x149e3
3, avc3.sys!StartProfilingTimer+0x16b97
4, avc3.sys!StartProfilingTimer+0x15b1a
5, avc3.sys!StartProfilingTimer+0x166f6
6, avc3.sys!SetAvckfStopRoutine+0x2d766
7, avc3.sys!SetAvckfStopRoutine+0x220bc
8, avc3.sys!SetAvckfStopRoutine+0x1997f
9, avc3.sys!DllUnload+0xc557
10, avc3.sys!StartProfilingTimer+0x1f4a0
11, ntoskrnl.exe!NtCreateFile+0x34e
12, ntoskrnl.exe!NtMapViewOfSection+0x1c0a
13, ntoskrnl.exe!NtDeviceIoControlFile+0x56
14, ntoskrnl.exe!KeSynchronizeExecution+0x3a23
15, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
16, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x1fb
17, wow64.dll!Wow64SystemServiceEx+0x1ce
18, wow64.dll!Wow64LdrpInitialize+0x42a
19, ntdll.dll!RtlUniform+0x6e6
20, ntdll.dll!EtwEventSetInformation+0x1da09
21, ntdll.dll!LdrInitializeThunk+0xe
22, ntdll.dll!NtDeviceIoControlFile+0x15
23, kernel32.dll!DeviceIoControl+0x48
24, avcuf32.dll!AvcGetJumpCode+0x1eb4d
25, avcuf32.dll!AvcGetJumpCode+0x3c94
26, avcuf32.dll!AvcGetJumpCode+0x1396f
27, avcuf32.dll!AvcGetJumpCode+0x3fb80
28, avcuf32.dll!AvcGetJumpCode+0x7c647
29, avcuf32.dll!AvcGetJumpCode+0xa43d
30, EMET.dll!GetHookAPIs+0x37e29
31, EMET.dll!GetHookAPIs+0x37d7b
32, ntdll.dll!RtlGetProcessHeaps+0x49d
33, ntdll.dll!RtlCaptureContext+0x187
34, ntdll.dll!RtlDestroyEnvironment+0x384
35, ntdll.dll!KiUserExceptionDispatcher+0xf
36, ntdll.dll!RtlEncodeSystemPointer+0x51f
37, ntdll.dll!RtlEncodeSystemPointer+0x65b
38, ntdll.dll!RtlEncodeSystemPointer+0x702
39, ntdll.dll!RtlEncodeSystemPointer+0x16e
40, ntdll.dll!RtlInitializeSid+0x3b
41, ntdll.dll!RtlEncodeSystemPointer+0x60f
42, ntdll.dll!RtlEncodeSystemPointer+0x702
43, ntdll.dll!RtlEncodeSystemPointer+0x16e
44, ntdll.dll!RtlInitializeSid+0x3b
45, ntdll.dll!RtlSetBits+0xf0
46, ntdll.dll!RtlSetBits+0x16b
47, ntdll.dll!RtlSetBits+0x60
48, ntdll.dll!RtlGetFullPathName_U+0x36d
49, ntdll.dll!RtlUlonglongByteSwap+0x68f
50, EMET.dll+0x27189
51, EMET.dll!EMETSendCert+0xff7
52, EMET.dll!EMETSendCert+0xebc
53, EMET.dll+0x27161
54, KernelBase.dll!SetThreadStackGuarantee+0xa37
55, KernelBase.dll!LoadLibraryExW+0x233
56, ntdll.dll!RtlQueryPerformanceCounter+0xa83
 
Labels: Needs-Feedback
Unable to reproduce the issue on Windows 7, Mac 10.11.5, Ubuntu 14.04 using 51.0.2704.106, latest canary 54.0.2800.0 as per above steps.

Please find attached screencast.

ow97@Could you please check the issue on clean profile and update the thread with screencast if issue still persists.
628552.mp4
264 KB View Download

Comment 2 by o...@outlook.com, Jul 19 2016

I am working on getting a screencast of the issue. However in the meantime here is some more detail:

I agree that the canary build is no longer affected

The issue is still present in the stable build even on a clean profile

Comment 3 by o...@outlook.com, Jul 19 2016

Here is a screen capture showing the issue
ScreenCapture_19-07-2016_14.mp4
15.2 MB Download
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 20 2016

Labels: -Needs-Feedback Needs-Review
Owner: ssamanoori@chromium.org
Thank you for providing more feedback. Adding requester "ssamanoori@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review Needs-Feedback
Owner: ----
Unable to reproduce the issue on Windows 7, Mac 10.11.5, Ubuntu 14.04 using 51.0.2704.106, latest stable 52.0.2743.82, canary 54.0.2809.0.

Please find attached screencast.
628552_latest stable.mp4
894 KB View Download
Components: Blink>Loader
Can you repro when you turn off your antivirus? The stack traces you posted are not in Chrome code.

Comment 8 by o...@outlook.com, Aug 16 2016

I don't have a debuggable copy of chrome at present, therefore I have had to get the stack traces externally. I will try get stack traces in safe mode, when I get a chance. (Probably at the weekend 20/08/16 - 21/08/16)
Project Member

Comment 9 by sheriffbot@chromium.org, Aug 24 2016

Labels: -Needs-Feedback Needs-Review
Owner: ssamanoori@chromium.org
Thank you for providing more feedback. Adding requester "ssamanoori@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Via-Wizard -Needs-Review Needs-Feedback
Owner: ----
Unable to reproduce the issue on Windows 7, Mac 10.11.6, Ubuntu 14.04 using latest stable 52.0.2743.116, canary 54.0.2838.2.

ow97@Could you please check the issue on latest chrome channels as per comment #7?
Project Member

Comment 12 by sheriffbot@chromium.org, Sep 24 2016

Status: Archived (was: Unconfirmed)
No feedback was received in the last 30 days from reporter "ow97@outlook.com", so archiving this. Please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment