[Bug] High CPU usage on main process

%3CLINGO-SUB%20id%3D%22lingo-sub-2404319%22%20slang%3D%22en-US%22%3E%5BBug%5D%20High%20CPU%20usage%20on%20main%20process%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2404319%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWhat%20went%20wrong%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20parent%20process%20takes%20up%20CPU%20resources%20heavily%20after%20an%20indefinite%20amount%20of%20time%2C%20and%20CPU%20usage%20remains%20elevated%20while%20being%20idle.%20In%20the%20case%20here%2C%20the%20parent%20process%20takes%20up%20about%20an%20entire%20core%20in%20a%2010-core%20system.%20Please%20refer%20to%20the%20screenshot%20below.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F285331i5ACCFC8578B25A95%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%221.png%22%20alt%3D%221.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhat%20is%20the%20expected%20behavior%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20CPU%20usage%20should%20remain%20low%20while%20being%20idle%2C%20and%20discarding%20tabs%20should%20give%20back%20resources%20to%20the%20system.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESteps%20to%20reproduce%20the%20problem%3A%3C%2FP%3E%3CP%3E1.%20Launch%20Microsoft%20Edge.%3C%2FP%3E%3CP%3E2.%20Use%20it%20for%20%22some%22%20time%20(say%20a%20few%20hours.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDid%20this%20work%20before%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ENo%2C%20since%20I%20was%20already%20having%20the%20same%20bug%20in%20version%2090.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20system%20specification%3F%3C%2FP%3E%3CP%3EMicrosoft%20Edge%3A%26nbsp%3B%3CSPAN%3EVersion%2091.0.864.37%20(Official%20Build)%20(64-bit)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EOperating%20System%3A%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EWindows%2010%20Pro%2021H1%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22line%22%3ECPU%3A%20Intel%20Core%20i9-10900K%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22line%22%3EGPU%3A%20NVIDIA%20GeForce%20RTX%203080%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22line%22%3ERAM%3A%2032GB%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESteps%20I%20have%20taken%20in%20an%20attempt%20to%20solve%20the%20issue%3A%3C%2FP%3E%3CP%3E1.%20Disabling%20extensions%20and%20testing%20each%20of%20them.%3C%2FP%3E%3CP%3E2.%20Clearing%20browsing%20data.%3C%2FP%3E%3CP%3E3.%20Reseting%20the%20browser.%3C%2FP%3E%3CP%3E4.%20Reinstalling%20the%20browser.%3C%2FP%3E%3CP%3E5.%20Repairing%20Windows%20files.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(Note%20that%20the%20above%20steps%20does%20not%20solve%20the%20problem%20since%20I%20have%20run%20into%20it%20again.%20Because%20of%20that%2C%20it%20leads%20me%20to%20believe%20that%20it%20is%20an%20existing%20bug%20within%20Edge.%20The%20only%20workaround%20now%20is%20to%20restart%20the%20application%2C%20but%20then%20the%20same%20issue%20comes%20up%20eventually%20after%20an%20indefinite%20amount%20of%20time.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20spent%20many%20hours%20doing%20my%20own%20investigation%20to%20pinpoint%20the%20issue%2C%20but%20I%20have%20not%20been%20able%20to%20come%20up%20with%20a%20conclusion.%20To%20help%20others%20investigate%20the%20problem%2C%20I%20have%20attached%20a%20trace%20file%20here.%20More%20information%20can%20be%20provided%20if%20it%20helps%20the%20process.%20I%20really%20hope%20someone%20who%20is%20knowledegable%2C%20can%20take%20a%20look%20and%20see%20what%20is%20causing%20the%20issue.%20Thanks%20for%20reading.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2404561%22%20slang%3D%22en-US%22%3ERe%3A%20%5BBug%5D%20High%20CPU%20usage%20on%20main%20process%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2404561%22%20slang%3D%22en-US%22%3EI%20also%20want%20to%20give%20a%20quick%20example%20in%20case%20someone%20comments%20that%20the%20level%20of%20CPU%20usage%20is%20normal%20here.%20Under%20normal%20working%20condition%2C%20playing%20a%201080p%2F1440p%2F2160p%20YouTube%20video%20in%20the%20background%20and%20browsing%20a%20couple%20of%20websites%20yield%20about%201-3%25%20CPU%20usage%20on%20average.%20I%20have%20benchmarked%20the%20performance%20against%20Google%20Chrome%20under%20the%20same%20conditions%20(extensions%2C%20settings%2C%20etc)%2C%20and%20it%20appears%20to%20be%20consistent.%20However%2C%20the%20bug%20is%20only%20exhibited%20in%20Edge.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2405479%22%20slang%3D%22en-US%22%3ERe%3A%20%5BBug%5D%20High%20CPU%20usage%20on%20main%20process%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2405479%22%20slang%3D%22en-US%22%3E%3CP%3EI%20decided%20to%20give%20it%20another%20try%20by%20doing%20a%20stack%20trace%20since%20I%20have%20just%20run%20into%20the%20same%20issue%20again%2C%20and%20the%20results%20confirmed%20that%20it%20is%20indeed%20a%20bug.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20see%20that%20%22RelaunchChromeBrowserWithNewCommandLineIfNeeded%20%2B%200x1ee5c8%22%20is%20called%20repeatedly%20by%20%22msedge.dll%22%2C%20which%20leads%20to%20high%20CPU%20usage.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22unknown.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F285416i8F609DDFAC85625F%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22unknown.png%22%20alt%3D%22unknown.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

What went wrong?

The parent process takes up CPU resources heavily after an indefinite amount of time, and CPU usage remains elevated while being idle. In the case here, the parent process takes up about an entire core in a 10-core system. Please refer to the screenshot below.

 

1.png

 

What is the expected behavior?

The CPU usage should remain low while being idle, and discarding tabs should give back resources to the system.

 

Steps to reproduce the problem:

1. Launch Microsoft Edge.

2. Use it for "some" time (say a few hours.)

 

Did this work before?

No, since I was already having the same bug in version 90.

 

What is the system specification?

Microsoft Edge: Version 91.0.864.37 (Official Build) (64-bit)

Operating System: Windows 10 Pro 21H1

CPU: Intel Core i9-10900K
GPU: NVIDIA GeForce RTX 3080

RAM: 32GB

 

Steps I have taken in an attempt to solve the issue:

1. Disabling extensions and testing each of them.

2. Clearing browsing data.

3. Reseting the browser.

4. Reinstalling the browser.

5. Repairing Windows files.

 

(Note that the above steps does not solve the problem since I have run into it again. Because of that, it leads me to believe that it is an existing bug within Edge. The only workaround now is to restart the application, but then the same issue comes up eventually after an indefinite amount of time.)

 

I have spent many hours doing my own investigation to pinpoint the issue, but I have not been able to come up with a conclusion. To help others investigate the problem, I have attached a trace file here. More information can be provided if it helps the process. I really hope someone who is knowledegable, can take a look and see what is causing the issue. Thanks for reading.

 

2 Replies
I also want to give a quick example in case someone comments that the level of CPU usage is normal here. Under normal working condition, playing a 1080p/1440p/2160p YouTube video in the background and browsing a couple of websites yield about 1-3% CPU usage on average. I have benchmarked the performance against Google Chrome under the same conditions (extensions, settings, etc), and it appears to be consistent. However, the bug is only exhibited in Edge.

I decided to give it another try by doing a stack trace since I have just run into the same issue again, and the results confirmed that it is indeed a bug.

 

You can see that "RelaunchChromeBrowserWithNewCommandLineIfNeeded + 0x1ee5c8" is called repeatedly by "msedge.dll", which leads to high CPU usage.

 

unknown.png