Issue 374624 in chromium: Running chrome causes 100% cpu usage of lsass.exe

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Bug-Regression OS-Windows

New issue 374624 by steven.h...@multiplay.co.uk: Running chrome causes 100%
cpu usage of lsass.exe
http://code.google.com/p/chromium/issues/detail?id=374624

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

Steps to reproduce the problem:
1. Load Chrome
2. View CPU details in Process Explorer for lsass.exe
3.

What is the expected behavior?
The CPU usage of lsass.exe should be very low

What went wrong?
The CPU usage of lsass.exe is 100% of core for a minute + when starting
chrome

Did this work before? N/A

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

There's a few posts around the net that this may be related to Chrome sync
but that's currently unconfirmed.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Labels: labelPerformance

Comment #1 on issue 374624 by a...@chromium.org: Running chrome causes 100%

cpu usage of lsass.exe
http://code.google.com/p/chromium/issues/detail?id=374624

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #3 on issue 374624 by steven.h...@multiplay.co.uk: Running chrome

causes 100% cpu usage of lsass.exe
http://code.google.com/p/chromium/issues/detail?id=374624

Lots of synced data yes, dashboard shows:-
Apps: 5, Extensions: 20, Settings: 181, Autofill: 2, Omnibox History: 1383,
Themes: 1, Bookmarks: 1210, PasswordsEncrypted: 1009, Open Tabs: 228

[chro...@googlecode.com]

Comment #4 on issue 374624 by adams...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
http://code.google.com/p/chromium/issues/detail?id=374624

I noticed today same problem on Windows Vista 32 bit.
I have Google Chrome 35.0.1916.153 m.

[chro...@googlecode.com]

Comment #5 on issue 374624 by ghclark...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
http://code.google.com/p/chromium/issues/detail?id=374624

Same issue with Win 7 64 bit and Chrome 35.0.1916.153 m

[chro...@googlecode.com]

Comment #6 on issue 374624 by arne.wol...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
http://code.google.com/p/chromium/issues/detail?id=374624

Fixed it by reinstalling Chrome

[chro...@googlecode.com]

Comment #7 on issue 374624 by mitch.hu...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
http://code.google.com/p/chromium/issues/detail?id=374624

I also experienced this with Win 7 x64 with Version 36.0.1985.143 m.
Reinstall appears to have fixed the issue for now. My lsass.exe would
spike to 50% CPU time after loading Chrome.

[chro...@googlecode.com]

Comment #8 on issue 374624 by srajesh....@gmail.com: Running chrome causes

100% cpu usage of lsass.exe

https://code.google.com/p/chromium/issues/detail?id=374624

same problem

[chro...@googlecode.com]

Comment #9 on issue 374624 by munl...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

same problem win 7

[chro...@googlecode.com]

Comment #10 on issue 374624 by benz...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Same problem with win7 64 bit and Chrome 37.0.2062.94 on a HP ProBook 4530s
(i5 processor with AMD Radeon Graphics).
I tried to reinstall it but the issue is still present; also with Chrome
Dev 38.0.2125.8 same problem.
With Chrome 34.0.1847 NO PROBLEM WITH LSASS.EXE

[chro...@googlecode.com]

Comment #11 on issue 374624 by acajamar...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Same problem with winxp and Chrome 36.0.1985.143

[chro...@googlecode.com]

Comment #14 on issue 374624 by f3fl...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe

https://code.google.com/p/chromium/issues/detail?id=374624

Two systems in my office got affected after Chrome updated from v.34 to
v.37 (current). Same behaviour - lsass.exe runs at full throttle (one core)
for 2 minutes, then Chrome starts. Not always reproducible, but happens
frequently. Both systems are Windows 7 x32.

[chro...@googlecode.com]

Comment #15 on issue 374624 by f3fl...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Here is a log made in Procmon - you can see lsass.exe doing a lot in
registry nonstop. The log did not start when the problem started, sorry -
so it starts when lsass is already actively consuming one core. Files here
(exported in all possible formats)
https://drive.google.com/folderview?id=0B7Gf-eniqaBzOExScW9RUlFhUFE&usp=sharing.
I can try to make a full log if it may help - tell me.

Besides, I noticed SAME behavior when opening specific Excel file. Excel
pops up but it's work area is white and it does not respond - lsass.exe
takes up one core, then I wait for a minute or two - then Excel starts
working. My thought is that these problems are related and MAY be not the
fault of Chrome but a combination of factors which make lsass.exe behave
this way and also affet other applications.

[chro...@googlecode.com]

Comment #17 on issue 374624 by chalker...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe

https://code.google.com/p/chromium/issues/detail?id=374624

I'm seeing this problem on Win 7 32-bit.

[chro...@googlecode.com]

Comment #18 on issue 374624 by corina.a...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Same problem on Win 7 64 bit

Chrome version: 41.0.2220.0 canary (64-bit)

[chro...@googlecode.com]

Comment #19 on issue 374624 by cmcrouss...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Same problem with Chrome on Windows 7 64bit.

[chro...@googlecode.com]

Comment #20 on issue 374624 by vitas.lo...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Allright it has been almost a year already. How can this bug still be
unconfirmed?? I have this problem on my Thinkpad T420 with Intel Core
i5-2540M with Win7 64bit and Google Chrome 39 which is 5 major versions
since the big was reported! As usually Google ignores people it seems...

[chro...@googlecode.com]

Comment #21 on issue 374624 by mikh.m...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Same problem with Chrome on Windows 7 64bit

sametime chrome does not startup
no viruses at laptop

[chro...@googlecode.com]

Comment #22 on issue 374624 by chalker...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

I resolved this on my machine. Turns out it was a really hard to find
virus/Trojan. Tried many virus programs and the only one that found it was
webroot.

[chro...@googlecode.com]

Comment #23 on issue 374624 by roscagal...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

It is really annoying to have this issue. I uninstalled chrome and can't
access my bookmarks now. I have a single core pc and lsass.exe just makes
it unusable. Reinstalling Chrome doesn't solve the problem. After closing
Chrome, one instance of Chrome.exe is still hanging and I have to kill it
in order to unfreeze the system.

@comment #22: can you tell me more about webroot and how you did fix the
problem?

[chro...@googlecode.com]

Comment #24 on issue 374624 by chalker...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Turns out this was a really obscure virus that none of my virus programs
picked up, including Sophos Enterprise virus. I knew it was a virus because
when opening Task manager, and then looking at resource monitor, I noticed
100's of network sockets being opened to obscure IP address. The virus
program that finally found it was Webroot SecureAnywhere Antivirus. I did a
30-day trial and cleaned it up. Once the virus was gone, all of the
lsass.exe CPU resources disappeared.

[chro...@googlecode.com]

Comment #25 on issue 374624 by vitas.lo...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

you have not provided any info about name of the virus, infected
files/processes or anything. So this information is useless unfortunately.
Could you please check the Webroot scan log or something and paste the
result here? But I doubt everybody here has a virus causing this lsass
several minutes cpu overload...
Interestingly enough my Win8.1 machine with Chrome does not suffer from
this behavior. Lsass.exe is completely calm there with Chrome

[chro...@googlecode.com]

Comment #26 on issue 374624 by chalker...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

I fixed this about 3 months ago and don't have the logs, sorry. I was
just trying to help, so apologize for the info being useless. Good luck.

[chro...@googlecode.com]

Comment #27 on issue 374624 by jd...@ionpcs.net: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

I am working on this issue right now.

Using some clues from you all here, I've tracked it down this.

Process explorer shows a security token request and termination loop
happening under lsass.exe, with token being <LaptopName>\<account>:1c42f

Such as: Smith_VAIO\John:1c42f

Upon inspection with Process Monitor, we see the following:

11:34:57.3492434 AM lsass.exe 908 RegQueryKey HKLM SUCCESS Query:
HandleTags, HandleTags: 0x0
11:34:57.3492833 AM lsass.exe 908 RegOpenKey
HKLM\Software\Microsoft\Windows
NT\CurrentVersion\ProfileList\S-1-5-21-563832473-1690269938-841482641-1000
SUCCESS Desired Access: Read
11:34:57.3493295 AM lsass.exe 908 RegQueryValue
HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList\S-1-5-21-563832473-1690269938-841482641-1000\ProfileImagePath
SUCCESS Type: REG_EXPAND_SZ, Length: 28, Data: C:\Users\John
11:34:57.3493613 AM lsass.exe 908 RegQueryValue
HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList\S-1-5-21-563832473-1690269938-841482641-1000\ProfileImagePath
SUCCESS Type: REG_EXPAND_SZ, Length: 28, Data: C:\Users\John
11:34:57.3493926 AM lsass.exe 908 RegCloseKey
HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList\S-1-5-21-563832473-1690269938-841482641-1000
SUCCESS
11:34:57.3495197 AM lsass.exe 908 CreateFile
C:\Users\John\AppData\Roaming\Microsoft\Protect\S-1-5-21-563832473-1690269938-841482641-513\Preferred
PATH NOT FOUND Desired Access: Generic Read, Disposition: Open, Options:
Sequential Access, Synchronous IO Non-Alert, Non-Directory File,
Attributes: HS, ShareMode: Read, AllocationSize: n/a, Impersonating:
Smith_VAIO\John


This behavior loops.

Sometimes throwing in:

11:34:57.1073869 AM lsass.exe 908 CreateFile
C:\Users\John\AppData\Roaming\Microsoft\Protect\CREDHIST SUCCESS Desired
Access: Generic Read/Write, Disposition: OpenIf, Options: Synchronous IO
Non-Alert, Non-Directory File, Random Access, Attributes: HS, ShareMode:
None, AllocationSize: 0, Impersonating: Smith_VAIO\John, OpenResult: Opened
11:34:57.1074461 AM lsass.exe 908 QueryStandardInformationFile
C:\Users\John\AppData\Roaming\Microsoft\Protect\CREDHIST SUCCESS
AllocationSize: 24, EndOfFile: 24, NumberOfLinks: 1, DeletePending: False,
Directory: False
11:34:57.1074769 AM lsass.exe 908 CreateFileMapping
C:\Users\John\AppData\Roaming\Microsoft\Protect\CREDHIST FILE LOCKED WITH
WRITERS SyncType: SyncTypeCreateSection, PageProtection:
11:34:57.1075034 AM lsass.exe 908 QueryStandardInformationFile
C:\Users\John\AppData\Roaming\Microsoft\Protect\CREDHIST SUCCESS
AllocationSize: 24, EndOfFile: 24, NumberOfLinks: 1, DeletePending: False,
Directory: False
11:34:57.1075669 AM lsass.exe 908 CreateFileMapping
C:\Users\John\AppData\Roaming\Microsoft\Protect\CREDHIST SUCCESS SyncType:
SyncTypeOther
11:34:57.1076805 AM lsass.exe 908 CloseFile
C:\Users\John\AppData\Roaming\Microsoft\Protect\CREDHIST SUCCESS



So...Using that info, I went to the
path "C:\Users\John\Appdata\Roaming\Microsoft\Protect\" and found one
folder with a random guid that was created days ago. lsass.exe was
currently still in a 'stuck' state, when I deleted this guid folder, and
another one was immediately created with a new guid. The next step is
probably unnecessary, but I deleted the newly created guid folder as well,
and this time it did not respawn. lsass.exe processor time was back to
normal. I attempted to close chrome, at which point it closed properly. I
reopened chrome, observed lsass use some cpu for about 10 seconds, then
stop. I closed chrome, and the process terminated properly yet again. I
then reopened chrome to observe the same behavior as previous (normal
behavior).

So, conclusion, the folder located
at "C:\Users\<username>\appdata\roaming\microsoft\protect\<guid>" must be
deleted.

That worked in my case.

Hope you value the info!

[chro...@googlecode.com]

Comment #28 on issue 374624 by dr.r...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

had same problem for about 5 months, lass.exe would consume 25% of CPU (it
would either hit one of 4 cores to 100% or spread the load across multiple
cores.
Monitoring system for multiple days indicates that lass.exe keeps CPU busy
more than 1% of total time system runs, which is way too high compared to
other processes.
I deleted folder as per "jd.." post, it seems to work for now.



Attachments:
lass.exe-high_cpu.PNG 6.5 KB

[chro...@googlecode.com]

Comment #29 on issue 374624 by dr.r...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Each time when chrome is started lass.exe will utilize cpu for just under a
sec CPU to 100%, barely noticeable.

I confirm issue is fixed after deleting the folder

"C:\Users\<username>\appdata\roaming\microsoft\protect\<guid>"

Note: if you have multiple local accounts, it needs to be done under every
account.

[chro...@googlecode.com]

Comment #30 on issue 374624 by jd...@ionpcs.net: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Issue has not reappeared for my user, thankfully.

[chro...@googlecode.com]

Comment #33 on issue 374624 by Trepanie...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

#27 #27 #27 #27 #27 #27 #27 #27 #27 #27 #27 #27

Thank god !!!

[chro...@googlecode.com]

Comment #34 on issue 374624 by l...@webpeoplemedia.com: Running chrome

causes 100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Can someone here explain this fix to me? I'm finding a ton of directories
and files in C:\Users\<username>\appdata\roaming\microsoft\protect\ and I
don't want to just guess at which one is supposed to be deleted. Is there
any theory behind this, or are you going by a timestamp, or basically, how
do you tell which one to delete? Thank you!

[chro...@googlecode.com]

Comment #35 on issue 374624 by l...@webpeoplemedia.com: Running chrome

causes 100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Actually, nevermind. Being a cautious soul I decided to just zip the most
recent guid and then delete the unzipped version. I restarted Chrome and
all is well--yay! Thank you all!

[chro...@googlecode.com]

Comment #36 on issue 374624 by DYSenior...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

I don't expect my situation to generate a lot of interest, but XP exhibits
similar behaviour by chrome/lsass. Needless to say, on a single-core
system the slowdown is far worse and lasts far longer. Strangely, desktop
updates [when Chrome closes, for example] are still horrendously slow even
an hour after CPU usage returns to zero [or thereabouts].

For a while I suspected that Avast! realtime scanning was a factor but
disabling that [and related features] had no beneficial effect.

FWIW: the

[chro...@googlecode.com]

Comment #37 on issue 374624 by DYSenior...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

I don't expect my situation to generate a lot of interest, but XP exhibits
similar behaviour by chrome/lsass. Needless to say, on a single-core
system the slowdown is far worse and lasts far longer. Strangely, desktop
updates [when Chrome closes, for example] are still horrendously slow even
an hour after CPU usage returns to zero [or thereabouts].

For a while I suspected that Avast! realtime scanning was a factor but
disabling that [and related features] had no beneficial effect.

FWIW: I couldn't find the "magic" folder anywhere in the filesystem.

[chro...@googlecode.com]

Comment #38 on issue 374624 by lrozenbl...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Confirming the issue on WinXP + Chrome 43.0.2357.124 m
Removing the user directory with GUID for ALL users on the system
unfortunately DIDN'T help

[chro...@googlecode.com]

Comment #40 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Created a new rule in the Firewall settings to block GoogleUpdate.exe file
and the problem disappeared under Windows XP SP3 indicating that the
culprit is the file consistently with the lsass.exe security function and
the problem appearance under various MS Windows.

[chro...@googlecode.com]

Comment #41 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Created a new rule in the Firewall settings to block GoogleUpdate.exe file
and the problem disappeared under Windows XP SP3 indicating that the

behavior of GoogleUpdate.exe and not a specific bug was the culprit
considering consistently with rather the security function of lsass.exe
than its specific version under various MS Windows.

[chro...@googlecode.com]

Comment #42 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Created a new rule in the Firewall settings to block GoogleUpdate.exe file
and the problem disappeared under Windows XP SP3 indicating that the
behavior of GoogleUpdate.exe and not a specific bug was the culprit

considering consistency with rather the security function of lsass.exe than

[chro...@googlecode.com]

Comment #43 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Created a new rule in the Firewall settings to block GoogleUpdate.exe
file and the problem disappeared under Windows XP SP3 indicating that the

culprit in 100 % CPU usage was the activation of the security function of
lsass.exe - regardless of its version under various MS Windows - by
GoogleUpdate.exe rather than a specific bug.
100 % CPU usage can be also reduced by increasing computer's RAM
(memory) to 4 GB (better to replace than to add) and setting the following
in Windows' System Properties->Advanced->Performance Options: (a) Visual
Effects to Adjust to best performance; (b) in Advanced: Processor
scheduling to Programs; Memory usage to System cache; and Virtual Memory to
Custom size 4096 MB both Initial size and Maximum size (150 % of the actual
RAM size, as shown in System Properties->General, would be better, but more
than 4 GB on one drive is not allowed under Windows XP).

[chro...@googlecode.com]

Comment #44 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Created a new rule in the Firewall settings to block GoogleUpdate.exe
file and the problem disappeared under Windows XP SP3 indicating that the
culprit in 100 % CPU usage was the activation of the security function of
lsass.exe - regardless of its version under various MS Windows - by
GoogleUpdate.exe rather than a specific bug.
100 % CPU usage can be also reduced by increasing computer's RAM
(memory) to 4 GB (better to replace than to add) and setting the following
in Windows' System Properties->Advanced->Performance Options: (a) Visual
Effects to Adjust to best performance; (b) in Advanced: Processor

scheduling to Programs; Memory usage to System cache; and in Virtual
Memory->Change->Custom size->4096 MB in Initial size and Maximum size
(150 % of the physical RAM size, as shown in System Properties->General,

would be better, but more than 4 GB on one drive is not allowed under

Windows XP); with more than 1 hard drive in the computer, it is better to
set up virtual memory Initial/Maximum size to: Drive C: 2/50 MB and Drive
[2nd]: 4096/4096, as described on http://aumha.org/win5/a/xpvm.php.

[chro...@googlecode.com]

Comment #45 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Created a new rule in the Firewall settings to block GoogleUpdate.exe
file and the problem disappeared under Windows XP SP3 indicating that the
culprit in 100 % CPU usage was the activation of the security function of
lsass.exe - regardless of its version under various MS Windows - by
GoogleUpdate.exe rather than a specific bug.
100 % CPU usage can be also reduced by increasing computer's RAM
(memory) to 4 GB (better to replace than to add) and setting the following
in Windows' System Properties->Advanced->Performance Options: (a) Visual
Effects to Adjust to best performance; (b) in Advanced: Processor
scheduling to Programs; Memory usage to System cache; and in Virtual
Memory->Change->Custom size->4096 MB in Initial size and Maximum size
(150 % of the physical RAM size, as shown in System Properties->General,
would be better, but more than 4 GB on one drive is not allowed under
Windows XP); with more than 1 hard drive in the computer, it is better to
set up virtual memory Initial/Maximum size to: Drive C: 2/50 MB and Drive
[2nd]: 4096/4096, as described on http://aumha.org/win5/a/xpvm.php.

Also, I disabled Automatic Updates in: Start->Control
Panel->Administrative Tools->Services->Automatic Updates->double
click->Startup type: Disabled & Service status: Stop(ped)->OK
(https://www.youtube.com/watch?v=-oVMiXpRIP4), and fixed IE8 (IE7) of SP3
as advised by Microsoft on
http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/windows-update-svchostexe-100-cpu-in-task-manager/6b372d8b-0ca4-4042-ba37-b2a7cdcdbd06
(SP2 on https://support.microsoft.com/en-us/kb/890582).

[chro...@googlecode.com]

Comment #47 on issue 374624 by wrjone...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

I have the same issue on vista with latest chrome - re-install did not fix
problem, have to abandon chrome at this time

[chro...@googlecode.com]

Comment #48 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Also, turned off the phishing and malware protection in Chrome, as well
as the anti-spam and anti-banner functions in the anti-virus software, but
not the mail anti-virus, web anti-virus, or firewall, which, all 3, are
essential to stay safe (in addition to slowing down computer file
anti-virus, if you download unknown files; slowing down network attack
blocker, if you use Wi-Fi/wireless network; IM anti-virus, if you use IM;
slowing down application control, if you allow to-/install free software
that is a bad idea, etc.).

[chro...@googlecode.com]

Comment #49 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

wrjone, 1st, clean up Chrom by disabling plug-ins and extensions,
especially Google Update,
(http://www.howtogeek.com/119191/browser-slow-how-to-make-google-chrome-fast-again/).
2nd, I believe memory leakage contributes to the problem. Check, if it
persists just after turning Vista up while with turned down anti-virus
software, especially any on-line (v. bad) whereas K------ky allows for
customization by turning down its not needed segments.
3rd, uninstall
(http://www.pcworld.com/article/2141881/beat-it-bloatware-how-to-clean-the-crap-off-your-pc.html)
all bloatware (https://en.wikipedia.org/wiki/Pre-installed_software) and
unnecessary freeware
(http://www.howtogeek.com/119191/browser-slow-how-to-make-google-chrome-fast-again/)
by removing (Start->Control Panel->Add or Remove Programs).
4th, disable any software you do not need at the computer's start
(Start->All Programs->Accessories->System Tools->System Configuration
Utility->Startup-) by unchecking each after googling its purpose).
5th, disable or set to manual (Start->Control Panel->Administrative
Tools->(Component Services)->Services (Local)->Standard) not needed
services in Windows XP
(http://www.blackviper.com/service-configurations/black-vipers-windows-xp-x86-32-bit-service-pack-3-service-configurations/
or Vista
(http://www.blackviper.com/service-configurations/black-vipers-windows-vista-service-pack-2-service-configurations/).

[chro...@googlecode.com]

Comment #50 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

[chro...@googlecode.com]

Comment #51 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

wrjone, 1st, clean up Chrom by disabling plug-ins and extensions,
especially Google Update,
(http://www.howtogeek.com/119191/browser-slow-how-to-make-google-chrome-fast-again/).
2nd, I believe memory leakage contributes to the problem. Check, if it
persists just after turning Vista up while with turned down anti-virus

software, especially any on-line (v. bad) whereas K------ky ($5 online for
1-3 desktop licences) allows for manual customization (others don't).

3rd, uninstall
(http://www.pcworld.com/article/2141881/beat-it-bloatware-how-to-clean-the-crap-off-your-pc.html)
all bloatware (https://en.wikipedia.org/wiki/Pre-installed_software) and
unnecessary freeware
(http://www.howtogeek.com/119191/browser-slow-how-to-make-google-chrome-fast-again/)
by removing (Start->Control Panel->Add or Remove Programs).
4th, disable any software you do not need at the computer's start
(Start->All Programs->Accessories->System Tools->System Configuration
Utility->Startup-) by unchecking each after googling its purpose).
5th, disable or set to manual (Start->Control Panel->Administrative
Tools->(Component Services)->Services (Local)->Standard) not needed
services in Windows XP
(http://www.blackviper.com/service-configurations/black-vipers-windows-xp-x86-32-bit-service-pack-3-service-configurations/
or Vista
(http://www.blackviper.com/service-configurations/black-vipers-windows-vista-service-pack-2-service-configurations/).

Also, I turned off: in Chrome - the phishing and malware protection; in
the K------ky anti-virus software (others disallow) - the anti-spam and
anti-banner functions, but not the mail anti-virus, web anti-virus, or
firewall, which (all 3) are essential to stay safe (in adition to slowing
down computer or network: the file anti-virus, if you download unknown
files; the network attack blocker, if you use Wi-Fi/wireless network; the
IM anti-virus, if you use IM; the application control, if you allow

to-/install free software that is a bad idea, etc.).

[chro...@googlecode.com]

Comment #52 on issue 374624 by ete...@gmail.com: Running chrome causes 100%

cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

& one more possible culprit: driver for Realtek chip sound card incl.
the soundman.exe file (Start->All Programs->Accessories->System
Tools->System Configuration Utility->Startup).

[chro...@googlecode.com]

Comment #53 on issue 374624 by Rapon...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

i cleaned visits history and glad

[chro...@googlecode.com]

Updates:
Cc: -srsrid...@chromium.org msrchan...@chromium.org

Comment #57 on issue 374624 by msrchan...@chromium.org: Running chrome

causes 100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Verified the issue on Latest Stable# 47.0.2526.80 and Latest Canary#
49.0.2586.0 on Windows and could not reproduce the issue.
@steven+old -- Could you please re-check on Latest versions mentioned and
update the issue.
Thanks in Advance.

[chro...@googlecode.com]

Comment #58 on issue 374624 by gotgar...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

See the same thing on Win7Pro 64

[chro...@googlecode.com]

Comment #59 on issue 374624 by gotgar...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

Just in case: Here is sku...@chromium.org and I have seen this on the
system every time Chrome starts.

[chro...@googlecode.com]

Comment #60 on issue 374624 by sku...@chromium.org: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

So, I have tried various things:
- Updated windows
- deleted the history to the end of time
- rebooted
- uninstalled Chrome,
- rebooted
- installed Chrome
- rebooted
- ..
But no matter what I do, as soon as I start chrome, one core of the CPU
gets pegged at 100% by lsass.exe. When quitting Chrome, the root process
(which does not have a window) remains active(?!?) and lsass.exe continues
too use 100% cpu time. When using the process explorer to kill that process
as well lsass.exe goes back to 0% CPU usage.

So what ever Chrome is doing, lsass.exe pegs one CPU on a Win7x64 system
(seen with latest public M47 build).

[chro...@googlecode.com]

Comment #61 on issue 374624 by niger...@gmail.com: Running chrome causes

100% cpu usage of lsass.exe
https://code.google.com/p/chromium/issues/detail?id=374624

upon reading comment #27 on
https://code.google.com/p/chromium/issues/detail?id=374624#c27
I have confirmed temporary resolution is to backup and then delete sub
folders inside folder located
at "C:\Users\<username>\appdata\roaming\microsoft\protect\". For several
times until lsass stops utilizing cpu.

also confirmed related (closed/not fixed) issue :
https://code.google.com/p/chromium/issues/detail?id=18744

Later went on web and searched this specific path and found following
article:
https://technet.microsoft.com/en-us/library/cc962112.aspx
Titled: "How Private Keys Are Stored"
And is in set of articles about EFS...

So some part of security/encryption inside our browsers are starting this
chain loop of errors. Probably because of bad implementation in WebKit
crypt API. Why I say WebKit? It's because I'we located this problem on
Opera 34 ("Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/47.0.2526.106 Safari/537.36 OPR/34.0.2036.47"). And what
Chrome and Opera share? is WebKit of course. I haven't encountered this
problem with any other software on my Windows 7.

Does not necessary relate that malicious plugins/addons are out of this
scope.
I have 10 addons so I will investigate this later, if problem reappears.

TIP: Use start > run : "shell:DpAPIKeys" to open "protect" folder.