brave-browser: NTDLL.dll crash, can't choose files, ... dialogs don't work anymore

@maximgeerinck one more step Chromium team was asking about; do you still experience the problem if you have a fresh profile?

Basically, you can either

1. rename or move the profile directory out of the way (you’ll see Chrome folder in C:\Users\username\AppData\local\Google; or for testing Brave, Brave-Browser folder in C:\Users\username\AppData\local\BraveSoftware)

OR

1. Try to run the browser from the command line with --user-data-dir="C:/path-here"

Given I just installed Chrome, it would assume so. However, i just made a new profile, and launched that. tried it again and it also crashes

Thanks for the follow up @maximgeerinck 😄 I shared that information in the Chromium ticket

I did run across this article: https://social.technet.microsoft.com/Forums/ie/en-US/61b44466-6e12-4258-bcb1-af77b2ad701e/ntdlldll-generated-for-application-after-installation-of-kb4343909-windows-10-1803?forum=win10itproapps

There are some steps we can try, if you’re willing 😄 What is being shown here makes sense - and I’m curious if this would solve the issue (even if just a temporary workaround)

1. Windows key => type Windows Security and hit enter
2. On the left of window, pick App & browser control
3. Under Exploit protection pick Exploit protection settings
4. Click Program settings
5. Choose the Add program to customize, then Add by program name and specify chrome.exe
6. Scroll down to Randomize memory allocations (Bottom-up ASLR), choose to override, and turn OFF
7. Try the steps that crash in Chrome again

If that still happens - you might try overriding some of the other program settings. It’s quite possible there’s a bug which is relying on the memory address remaining the same

Whatever change i make, it doesn’t seem to work, it keeps crashing.

Chrome, Brave, they both crash even though i tried many different options in that panel.

Interestingly, Microsoft Edge (Chromium based), does work.

details:

Microsoft Edge | 92.0.902.73 (Official build) (64-bit)
-- | --
Revision | cad199e39220991414cd71868a619fff614880c7
Operating system | Windows 10 OS Version 2009 (Build 19043.1165)
JavaScript | V8 9.2.230.22
User agent | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36 Edg/92.0.902.73

Exactly.

This was with all save file dialogs. However, since a recent update, it’s now only for save dialogs resulting from “Save to pdf” (for example when printing)

@maximgeerinck nice - that looks like an officially supported program; I’m trying to find similar reports. Does the crash happen if your window is regular? (ex: it’s not snapped into place using FancyZones)?

Indeed, it also happens when the window was not snapped into place. It also happened in safe mode (where fancy zones is not loaded).

I think it’s a bug in chromium because i also have this with chrome