Description of the issue:
I cannot open a new private window unless there is already a non-private brave window. Using either the windows icon context menu task or starting brave from the command line with the “–incognito” option while no other brave windows are running will result in brave crashing immediately.
I have found the following otherhttps://community.brave.com/t/high-cpu-usage-when-have-dexscreener-com-tabs-opened/494493 posts with no replies suggesting this bug has existed since 2019:
- Open Private window using right click does not start independent Brave browser
- Brave Open Private Window First, Crashing
How can this issue be reproduced?
Option 1: Context Menu
- Close all instances of Brave
- Find Brave in Windows Start Menu
- Right Click Icon to open context menu
- Select “New Private Window” from tasks
- Brave will start and then crash
Option 2: Command Line
- Close all instances of Brave
- Open Command line
- Navigate to brave install directory
- Run “brave.exe --incognito”
- Brave will start and then crash
Expected result:
Brave should open a new private window
Brave Version( check About Brave
):
Version 1.52.129 Chromium: 114.0.5735.198 (Official Build) (64-bit)
Additional Information:
Issue reproduced on Windows 10 Version 22H2 Build 19045.3086
Created a crash dump from incident, available on request. Summary:
0:000> !analyze
-
*
-
Exception Analysis *
-
*
PROCESS_NAME: brave.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
SYMBOL_NAME: chrome+d41be7
MODULE_NAME: chrome
IMAGE_NAME: chrome.dll
FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_chrome.dll!Unknown
FAILURE_ID_HASH: {74d388af-6d1f-21b1-987e-9640e41d45b8}
Followup: MachineOwner
0:000> k
Child-SP RetAddr Call Site
00 000000ff38bfd370 00007ffb
52964993 chrome!GetHandleVerifier+0xd41be7