Bug: Blank private window uses 100% CPU!

Feedback Developer Builds
1

When opening a blank private window, Brave Dev uses 100% constantly. This seems to be a new phenomenon in Brave Dev version 1.32.82 Chromium: 95.0.4638.54 (Official Build) dev (64-bit) I hope this can be fixed quickly since it pretty much makes private windows useless… :frowning: I’ll try reverting to the previous version and see if that helps.

EDIT: Confirmed, 1.32.77 does not have this issue.

1 Like
2

Found this github issue, which is the same bug:

3

Ping @Mattches - Could you notify the team about this issue? It feels urgent to solve it before it reaches the release track. Thanks!

4

@jek6094,
Does disabling Hardware Acceleration in settings resolve the issue?

You’ll find this in Settings --> Additional Settings --> System --> Hardware Acceleration

5

No, it’s still the same. I did take a stack snapshot of the most active thread in one of the two new processes that start when the private window opens, and it looks like this:

ntoskrnl.exe!KiCpuId+0xaa
ntoskrnl.exe!ObfReferenceObject+0x792
ntoskrnl.exe!KeWaitForSingleObject+0x1a3
ntoskrnl.exe!CcGetFlushedValidData+0xc34
ntoskrnl.exe!KeInsertQueueApc+0x605
ntoskrnl.exe!ObfReferenceObject+0x99d
ntoskrnl.exe!KeWaitForSingleObject+0x1a3
ntoskrnl.exe!NtWaitForSingleObject+0xde
ntoskrnl.exe!longjmp+0x5bf3
ntdll.dll!ZwWaitForSingleObject+0xa
KERNELBASE.dll!WaitForSingleObjectEx+0x9c
chrome.dll!CrashForExceptionInNonABICompliantCodeRange+0xb3e801
chrome.dll!RelaunchChromeBrowserWithNewCommandLineIfNeeded+0x15d7b8
chrome.dll!RelaunchChromeBrowserWithNewCommandLineIfNeeded+0x16beb8
chrome.dll!CrashForExceptionInNonABICompliantCodeRange+0xaecc32
chrome.dll!argon2_encodedlen+0xafed6
chrome.dll!ChromeMain+0x1e4c098
chrome.dll!ChromeMain+0x1e4b3c4
chrome.dll!ChromeMain+0x1ac
brave.exe!GetPakFileHashes+0x1433
brave.exe!GetPakFileHashes+0xba0
brave.exe!GetHandleVerifier+0xa8662
kernel32.dll!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x1d

Here is a snapshot of the process activity with an empty private window launched:

brave-cpu-usage

(The two lowest processes are created when the private window opens)

6

@jek6094,
Do you have any extensions installed and running in the browser? Also, when you test this, do you have only the Private window open? Or do you also have your standard browser window open as well?

7
  • Tried with all extensions disabled, no difference.
  • Tried closing the standard window, no difference.

It looks like they are getting closer to nailing which commit that introduced this when looking at the github issue, so hopefully it will be fixed soon.

8

I think I found it! If you disable brave://flags/#native-brave-wallet, it doesn’t happen.

1 Like
9

Had the same issue but disabling that flag seems to have fixed it

10

@jek6094,
Thank you for updating us here. I’ll be sure to pass this information onto the team for further review.

1 Like