Error 'Breakpoint A breakpoint has been reached.' occurred while running cefsharp.browsersubprocess

[Nachtinho]

Is there an existing issue for this?

• I have searched both open/closed issues, no issue already exists.

CefSharp Version

130.1.90.0

Operating System

Windows 11

Architecture

x64

.Net Version

.NET 4.8

Implementation

OffScreen

Reproduction Steps

Recently, a problem has arisen with the Cefsharp browser (see title).

We start the browser through a C# process that launches a Windows console application in which the Cefsharp browser is implemented.

When I run the calling process as an administrator, it works.
When I directly invoke the console application, it also works.
However, when I start the process as a normal user, an error message appears in a dialog, and the process aborts.

I have created a debug.log with following entries:
[32080:28904:1127/090839.916:VERBOSE1:partitioned_lock_manager.cc(187)] All locks acquired for Start@chrome\browser\web_applications\generated_icon_fix_manager.cc:58
[32080:28904:1127/090839.916:VERBOSE1:partitioned_lock_manager.cc(229)] Releasing {id: 0x31, partition: 0} requested by Start@chrome\browser\web_applications\generated_icon_fix_manager.cc:58
[32080:28904:1127/090839.934:FATAL:check.cc(361)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!

while running as an administrator, I found the same entries but the last one.
Instead it continues with this:
[21324:33072:1127/092141.745:VERBOSE1:frame_host_impl.cc(573)] frame 5-32EC81229C8F4130E3DCC5A6453C4971 (main) detached (reason=RENDER_FRAME_CHANGED, is_connected=0)

Expected behavior

Should not throw this error

Actual behavior

throws exception in a dialog and stops

Regression?

It happens with older versions, too

Known Workarounds

works as administrator

Does this problem also occur in the CEF Sample Application

Not Tested

Other information

No response

[amaitland]

Converting to discussion as this is unlikely a bug as two out of three run successfully.

When I directly invoke the console application, it also works.
However, when I start the process as a normal user, an error message appears in a dialog, and the process aborts.

What's the difference between the two? You'll need to do some investigation. Working directory? etc